Closed Bug 24525 Opened 25 years ago Closed 23 years ago

Inital Nav window placement wrong on MacOS

Categories

(SeaMonkey :: UI Design, defect, P4)

PowerPC
Mac System 8.5
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME
mozilla1.1alpha

People

(Reporter: saari, Assigned: saari)

References

Details

(Whiteboard: [nsbeta2-][nsbeta3-])

Attachments

(1 file)

Initial Navigator window placement is wrong on MacOS with two monitors. My setup has a smaller monitor on the left, with the larger primary (has menubar) monitor on the right. The initial window placement is relative to the top of the primary monitor, and the left edge of the secondary monitor. Since I have my smaller monitor down and to the left, the initial Navigator window comes up halfway off the top of the smaller screen on the left. Also, I left the last window on the primary monitor, so it should really be coming up on the primary monitor.
m15 Need a mac person to help here, pinkerton?
Assignee: don → pinkerton
Target Milestone: M15
bulk accepting xpmenu/popup bugs. sigh.
Status: NEW → ASSIGNED
what do that apple ui guidelines say about initial window placement and primary monitors? What does 4.x do in this same case?
Try and remember where you were and go back there. We don't do that. If you can't remember where you were, go to the primary screen. We don't do that. If all else fails, make sure you're actually onscreen. We don't do that correctly in this situation.
Depends on: 23380
Pink I can take this if you want. I need to move the initial window placement logic higher up anyway.
go for it.
Assignee: pinkerton → saari
Status: ASSIGNED → NEW
Mass-moving most M15 bugs to M16
Target Milestone: M15 → M16
Status: NEW → ASSIGNED
changing qa contact on selected bugs from paulmac to elig@netscape.com
QA Contact: paulmac → elig
Keywords: nsbeta2
Priority: P3 → P1
Whiteboard: [nsbeta2-]
[nsbeta2-]
Mass-moving nsbeta2- bugs to M20
Target Milestone: M16 → M20
This has to get fixed because it is messing up window placement on other platforms, and preventing things like moving a window offscreen for a while. (the printing implementation wants to do this)
Keywords: nsbeta3
Whiteboard: [nsbeta2-] → [nsbeta2-][nsbeta3+]
Target Milestone: M20 → M18
P4, since it affects only a very small percentage of users.
Priority: P1 → P4
Please note that we are not committing to fix P4/P5 bugs for N6, although we could still work on a fix in priority order, or take a patch.
Bad bug...
no time left for this, nsbeta3-/future
Whiteboard: [nsbeta2-][nsbeta3+] → [nsbeta2-][nsbeta3-]
Target Milestone: M18 → Future
Keywords: mozilla0.9
Would be nice to fix for mozilla 1.0
Target Milestone: Future → mozilla1.0
This duplicates #13180 and blocks #4252. The small percentage of users that are encountering this is true BUT then where I work all mac users have two screens and all have important roles in defining browser support for new sites, making this critical evangelization vise as I think this applies to most web design agencies worldwide.
Blocks: 4252
Yes, 2 screens are very common on Macs. Saari, please reevaluate and fix for mozilla0.9, if anyhow possible.
I know they're common, I run with 2 screen on a Mac, even with one in the dreaded negative coordinate system :-) I targeted 1.0 because it isn't as critical as crashes, speed and memory IMO. But, I'll put it on the 0.9 radar with no promises (there is a LOT of work to be done).
Target Milestone: mozilla1.0 → mozilla0.9
Is bug #36473 a duplicate of this bug? We need a new QA contact on this bug. Here is a comment from Clint McIntosh on 11/15/2000 at http://www.macintouch.com/netscape6.html (who also sees problems): I have 2 monitors connected to my PowerComputing clone. When the first splash screen for the Netscape 6 program appeared, it straddled my monitors. If it were centered, I might be able to understand, but it was split 70-30 between the monitors! When I opened the preferences screen it came up on my second monitor - not the primary - and even then it was like someone moved the window half way off the screen. Subsequent launches still put the browser window itself in my secondary monitor even after I quit the program with it in my primary monitor!
Keywords: nsmac2
*** Bug 36473 has been marked as a duplicate of this bug. ***
Is this a duplicate of #13180 (or vice versa)?
Here is a comment from Joshua Goldberg on 11/15/2000 at http://www.macintouch.com/netscape6.html: On my two monitor system, the splash screen, preferences windows and popups are divided between both monitors; I have to move the window every time.
Well, yes, effectively this bug is pretty much the same as bug 13180. That one is more an architectural complaint which makes note of the fact that the DOM, which we use everywhere for window placement, doesn't really understand the concept of multiple monitors at all. This one complains about a specific instance of what is probably an aspect of 13180. Truth, I'm not looking at it. I thought we had this fixed. I should probably get a second monitor long enough to verify that. I don't understand Joshua's complaint. I believe the splash screen is handled specially, and shouldn't be subject to DOM vagaries. Wants checking, I guess. But anyway, more information about his system would be useful for understanding why windows initially show up split. Regardless, they should only do that once, until placed by hand, where they should stick. Works for me, anyway. Though I occasionally hear that it doesn't work for some people. Usually it's not reproducible. If he cares to file a bug with specifics, we could work on it. As the complaint you copied is worded, it disagrees with my experience in some ways, so I couldn't promise a solution.
QA Contact: elig → jrgm
Target Milestone: mozilla0.9 → mozilla1.0
nominating for dogfood (from sdagley's list of bugs that are good candidates for our next release)
Keywords: nsdogfood
Keywords: nsCatFood
Keywords: nsdogfood
Is this still a problem? Sorry, not running with multiple monitors these days.
Keywords: mozilla1.0
Target Milestone: mozilla1.0 → mozilla1.1
Repeating the request for anyone to confirm this bug still exists. Bueller?
I don't see the problem mpt reported on a single-monitor setup (using a new profile). I don't have two monitors to test with; does anyone else?
our window placement code changed 6-8 months ago. i'm assuming this isn't a problem anymore. ben would be the one to talk to, he wrote the new code.
Ok, I setup a dual monitor Mac and tested this under Mac OS X 10.1.3 - no problem noted with the Moz 0.9.8 build. Closing as WORKSFORME
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: