Closed
Bug 1005620
Opened 12 years ago
Closed 3 months ago
[mac os x / cocoa] Using dual monitors, Firefox/Thunderbird opens in wrong monitor
Categories
(Core :: Widget: Cocoa, defect, P2)
Tracking
()
RESOLVED
DUPLICATE
of bug 875858
People
(Reporter: sawrubh, Unassigned)
References
Details
(Whiteboard: [mac:multimonitor])
Attachments
(1 file)
|
1.47 KB,
patch
|
Details | Diff | Splinter Review |
This is the bug for tracking the Mac OS X specific fix for bug 264030.
Updated•12 years ago
|
Summary: Mac OS X tracking bug for 264030 → [mac os x / cocoa] Using dual monitors, Firefox/Thunderbird opens in wrong monitor
Comment 1•12 years ago
|
||
The nsCocoaWindow.mm part makes sense to me (and would get my r+). The nsXULWindow.cpp part should probably be reviewed by neil@httl.net. Has somebody tested that that part on non-Mac platforms?
Comment 3•12 years ago
|
||
Note for anyone interested in this bug:
The nsXULWindow.cpp change has been landed as a part of bug 1005619 with a few modifications to prevent bug 30116 from regress.
Now all you have to do is implementing nsIWidget::GetRestoredBounds() on Mac OS X. Unfortunately I don't know how to implement it.
Updated•10 years ago
|
Priority: -- → P2
Whiteboard: tpi:+
Updated•10 years ago
|
Flags: needinfo?(twalker)
Comment 4•10 years ago
|
||
Mac 10.11, Nightly 49.0a1, 20160504043118
If you have Preference | General | When Nightly starts: set to "Show my windows and tabs from last time" then Nightly opens on the correct screen as expected. However, if you have that same preference set to either of the other two options, "Show my home page" or " Show a blank page", then Nightly opens in its default location. Note: If your home page is set to about:home, clicking Restore Previous Session will send browser window to the correct screen/monitor.
Flags: needinfo?(twalker)
Updated•9 years ago
|
Whiteboard: tpi:+ → [tpi:+][tpi-help-requested]
Updated•5 years ago
|
Whiteboard: [tpi:+][tpi-help-requested] → [mac:multimonitor]
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•