Screen resize or print does a refresh with loss of information if a timeout occurs



13 years ago
12 years ago


(Reporter: sturges, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)




13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041210
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a6) Gecko/20041210

Resizing a Browser pane or doing a print does a refresh of the source data. 

If there has been a timeout the display contents can be permanently lost.

Reproducible: Always
Steps to Reproduce:
1. On sensitive sites [with built in timeouts for security] a screen which is
nicely displayed cannot be printed or resized without the information being lost
if the timeout period has passed.
2. If the display is a one time event [like an order confirmation] it may not be
possible to ever recover the lost display of the event in question.

Actual Results:  
Resize or print not possible if a timeout [for relogin] has occurred.

Expected Results:  
Contents of any screen should be printable or resizable at anytime after the
screen has been obtained from the website.
I've never encountered this problem.  What site are you seeing this on? 
Printing certainly uses the data currently displayed, and so does resizing
unless the page does something weird with onresize events...
Version: unspecified → Trunk
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:
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.
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.