Closed Bug 557429 Opened 14 years ago Closed 14 years ago

oversize window impossibly placed on 2nd monitor

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: treyfore, Unassigned)

Details

(Whiteboard: [CLOSEME 2011-1-30])

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3

A window dragged into a smaller secondary display,
reopens (after FF restart) with bottom rather than top

Reproducible: Always

Steps to Reproduce:
1.Drag 1280x1024 FF window into 1440x960 display.
2.Restart FF.
3.Behold 1280x1028 window opened on 1440x960,
but with bottom of 1028 aligned to bottom of 960.
(Titlebar and controls are inaccessibly off screen.)

Actual Results:  
1280x1024 FF window opens on correct (secondary, 1440x960) monitor.
Problem: bottom edge of the 1024 height is aligned to bottom of 960.
Thus, titlebar and window controls are offscreen and inaccessible.

Expected Results:  
When the window is first moved, titlebar and controls are within mouse reach.
Expect original alignment, or at least to have controls available.
(Perhaps refuse to open window with controls out of view?)

I'll try to reproduce on OS X.
Maybe related to bug 463379 comment 1 or Core bug 394843?
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
OS: Windows 7 → Windows XP
Resolution: --- → FIXED
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.