296288 - Problem with jscript resizing script after print preview.

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Ximin Luo]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Before printpreview, resizing the browser window also triggers the
resizing-script on the stated webpage, which runs correctly and resizes and
repositions the various webpage elements so make it look "normal" again.

However, after printpreview, resizing the window does trigger in part the
resizing-script on the stated webpage, but the right and bottom values of the
various elements in the webpage are NOT resized and repositioned, cutting it out
of the display. This is NOT a problem with the script on the webpage, as it runs
perfectly before printpreview. This bug is FF-specific, as the script also runs
perfectly after printpreview in MSIE.

I concluded that Firefox fails to recalculate browser window size values upon
resizing after print preview. However,
javascript:alert(window.innerWidth/Height); after printpreview still gives the
correct value, even though the webpage resizer script (which generates values
based on the browser's innerWidth/Height variable) does not work properly then.

Reproducible: Always

Steps to Reproduce:
1. open http://webxl.5gigs.com/?bugs.html
2. try resizing the window. you'll notice the page automatically resizes itself
when you let go of the mousebutton.
3. now open print preview.
4. try resizing the window now
Actual Results:  
5. the page does not re-adjust correctly. the scrollbuttons on the right are
drawn outside the browser window, and the border on the left-center extends into
the bottom 

Expected Results:  
5. the page should have resized correctly, with the left-center border being
redrawn at the right size, and the scrollbuttons being redrawn within the
browser window.

the bug corrects itself when the page is reloaded. in other words, after you
reload the page the resizer-script works properly again.

Comment 1

[Ximin Luo]

sorry, i missed out a step in "how to reproduce"

3b: close print preview

Comment 2

[Ximin Luo]

I think I have an idea of the cause behind the bug now.

on my site there is a show/hide menus button. this calls, essentially, the same
functions as the auto-resizer-script.

after printpreview, the show/hide buttons still works perfectly. however, the
auto-resizer-script doesn't

this is the code I am using for the autoresizer.
window.onresize = resizeFix;

maybe, after printpreview the browser no longer recognises user-action triggers
in the <script> tag?

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

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.