Closed
Bug 510736
Opened 15 years ago
Closed 14 years ago
Windows open on wrong monitor in maximized mode (multimonitor setup)
Categories
(Core :: Widget: Win32, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 264030
People
(Reporter: zoiled, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1pre) Gecko/20090717 SeaMonkey/2.0b1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.1pre) Gecko/20090717 SeaMonkey/2.0b1 If SeaMonkey 2.0B1 is closed in maximized mode it don't remember what monitor it was closed on. In "normal" mode e.g. not maximized it works as expected. (PS! if someone fix this please remember that some have their third monitor to the left of their mainmonitor (negative x/y offsets). Reproducible: Always Steps to Reproduce: 1. Go from maximized to normal window mode 2. Move window to another monitor 3. Maximize it there 4. Un-maximize and move window to primary montor 5. Maximize 6. Close seamonkey 7. Open seamonkey. Seamonkey does NOT open on the primary montor but the one in step 2. Actual Results: SeaMonkey does not open on the monitor I expect (the one it was closed on). It rather opens on the monitor it was last maximized on. Expected Results: SeaMonkey should open as it was closed. E.g. in the same state (maximized, normal) and on the monitor it was last closed on. The same bug was in the old SeaMonkey 1.x suite and Mozilla 1.8 I flagged this as Severity: Normal since I think it's not obvious to most people how to work around this issue. (the workaround is to close the window unmaximized on the monitor you want it to open on again).
Comment 1•15 years ago
|
||
I didn't know that it would remember any monitor in any case, but it sounds to me like a platform problem. Does Firefox 3.5 act correctly?
Comment 3•15 years ago
|
||
OK, thanks, then it's really a Mozilla platform problem. I suspect Widget: Win32 for now, people there will hopefully know better if that's right or it belongs somewhere else.
Component: OS Integration → Widget: Win32
Product: SeaMonkey → Core
QA Contact: os-integration → win32
Comment 4•15 years ago
|
||
I just tested it, it's still there and the work around works fine.
Yup Same problem with SeaMonkey 2.0 - I guess the bug should change status to confirmed now? ;)
Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729) Exactly the same problem in Firefox.
This week I have upgraded to Thunderbird 3.0 and there is exactly same problem. I have this problem with Firefox 3 (User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729)). I'm using multimonitor all of my work time and this "feature" (yep, it's bug) bored me very much.
Could someone with the appropriate rights change the Status to Confirmed please?
Updated•14 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Duplicate of bug 465240?
Comment 10•14 years ago
|
||
Looks like it, though the title ("Maximize status does not store the screen") really made me wonder what it was on about :)
Comment 11•14 years ago
|
||
bug 264030 should probably move to a component where it can get *fixed*.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•