209957 - Acrobat plugin offset it window after screen saver operates.

Status: RESOLVED WORKSFORME

(Core Graveyard :: Plug-ins, defect)

Description

[Doug Thistlethwaite]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3.1) Gecko/20030425
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3.1) Gecko/20030425

The Acrobat Reader plugin version 5.1 is rendered in the lower right quarter of
screen when Sach Marine Aquaium v2 screen saver is stopped.  This does not
happen with simpler screen savers.

I am pretty sure this particular screen saver changes the display resolution
when it is running and returns it to the user setting when is exits.

Reproducible: Always

Steps to Reproduce:
1. Bring up a acrobat doc.
2. Allow screen saver to start -or- manually start it in preferences.
3. Move cursor to exit screen saver.
4. The Acrobat plugin is now in the lower right corner of the mozilla window.

Actual Results:  
It seems I have to exit the mozilla window and reload the pdf file to get the
display right.

Expected Results:  
render the acrobat display in the same place as before.

Comment 1

[Doug Thistlethwaite]

I noticed a couple more things.

1. The 3/4 area where the acrobat reader should be is not updated.  If you bring
a window over the mozilla window, its image will fill the area where the acrobat
reader is missing.

2. Resizing the mozilla window also seems to fix the display.

Comment 2

[Rob Jaworski]

Sounds like a refresh issue.

Does this still happen with current builds of everything (ie, mozilla/ff, Acrobat)?

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Doug Thistlethwaite]

I tested this on a system running XP Pro and FireFox 1.0.6 and it is no longer a
problem.

Comment 5

[Adam Guthrie]

Thanks for your help, Doug.