Closed Bug 256186 Opened 21 years ago Closed 20 years ago

Firefox page rendering broken when resizing from 1600x1200 to 1024x768

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: jahn2001, Assigned: bugzilla)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3 I usually work at a 1600x1200 resolution. However, when I access my computer via RDP connection, the screen resolution gets changed to 1024x768. Firefox itself seems to be able to handle this change, the window gets correctly resized. However, the renderer still seems to think it's at 1600x1200: the horizontal scroll bar disappears and tables and text will be 1600 pixels wide with no vertical scrollbar appearing, so the web page content beyond 1024 pixels is not readable. I can fix this problem only by closing Firefox and reopening at 1024x768. When I open Firefox in 1024x768, change the resolution to 1600x1200 and later change back to 1024x768, the problem does not occur. This problem does also not occur with Mozilla, but has occurred at least since Firefox 0.6. Reproducible: Always Steps to Reproduce: 1. Run Firefox in 1600x1200 2. Access the computer via MS Remote Desktop Client in 1024x768 3. Try to access a dynamically resizing web page, e.g. www.slashdot.org Actual Results: No horizontal scroll bar, no vertical scroll bar, content 1600 pixels wide. Expected Results: Horizontal scroll bar, vertical scroll bar appearing, content 1024 pixels wide.
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.