Windows open in very different locations on RedHat 6.0 and WinNT (both are 102808 builds). 1. Load http://client/demo/external/gecko/eden/eden1028/default.html 2. Click "here"; new window opens (different locations on WinNT and Redhat) 3. Click "signon" (you're not really signing in); two new windows open -- one is long vertical bar. Both these appear is significantly different locations for WinNT and Redhat6.0. We want the Redhat 6.0 placement to operate like the WinNT. In other words, the WinNT placement is how the windows should appear. Perhaps an easier problem is solve is just a way to control new window placement on RedHat. For teh demo, we don't need the NT and Redhat to be same. thx, kevin
This isn't really a layout issue. At least at far as I'm aware we don't choose the window location Reassinging to XPApps. Hopefully Gramps knows who this goes to
Component: Layout → XPApps
Summary: [PDT] [DEMO] [PP] Significantly different opening window locations → [PP] Significantly different opening window locations
Setting to XP Apps component. Agreed at PDT mtg today that this is not a blocker for [DEM0], thus removing that from Summary.
Off to pav since he's the X11 window maestro ...
I can fix this by commenting out one line of code if anyone is interested.
Pavlov, I'm interested! Maybe we can get together later today or tmrw (lots of mtgs today). I'll come find you by end of day tmrw or feel free to drop by anytime. Again, Wed's (today) are tough, though. thx, kevin
Summary: [PP] Significantly different opening window locations → [DEMO] [PP] Significantly different opening window locations
The original content workaround that allowed us to make this NOT a [DEMO] bug doesn't work due to some issues w/ xwindows (Pavlov's the expert here). Easiest fix is to make Pavlov's very simple, one or two-line code change in a branch off M11. How does this sound to PDT? thx, kevin
so, kevin, are you getting your linux build system ready to apply pav's patch? ;-)
Component: XPApps → XP Toolkit/Widgets
Summary: [DEMO] [PP] Significantly different opening window locations → [DEMO] [PP] Can't move toplevel windows to specific coordinates on the desktop
Target Milestone: M12
Summary: [DEMO] [PP] Can't move toplevel windows to specific coordinates on the desktop → [DEMO-] [PP] Can't move toplevel windows to specific coordinates on the desktop
Severity: critical → normal
Priority: P1 → P2
Summary: [DEMO-] [PP] Can't move toplevel windows to specific coordinates on the desktop → [PP] Can't move toplevel windows to specific coordinates on the desktop
Taking this off the [DEMO] radar. I've figured out a workaround. Platform parity bug is still legit. Much less urgent though. thx, kevin
Mass-moving non-PDT+ bugs to M13
Adding "pp" keyword.
Putting on beta1 radar.
This should be fixed on Linux because not having this means that windows will never go where they are told and a lot of webpage js code doesn't work right.
Can you give an example of some top100 sites that have this problem?
Updating QA contact.
QA Contact: petersen → paulmac
Can you give me a list of the "top100" sites?
um. hello. if you are going to ask me for a list of the top100 sites so I can answer your question, give them to me before you mark this PDT- or at least give me some reason.
top100 list sent to pavlov. Adding [NEED INFO] to Status Summary.
Whiteboard: [NEED INFO]
*** Bug 26918 has been marked as a duplicate of this bug. ***
pav, any update on this?
ok. after viewing most of the top100 sites (the ones that didn't crash) I was unable to find any pages (other than AOL and Netscape.. heh) that pop up windows on their main page. These two don't specify x and y coordinates for them though.
Status: ASSIGNED → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED
please ignore, massive spam giving email@example.com backlog of XPToolkits resolved fixed bugs to verify
QA Contact: paulmac → jrgm
Moving this bug to all groups so that anyone can view it. It was mentioned in a news post and people on IRC were asking about it, and I cannot see any netscape-specific information in the bug, apart from the URI to which it points. Since no-one outside netscape can read that page anyway there is no problem with having this bug available as far as I can see. Please accept my apologies if I was wrong to do this.
You need to log in before you can comment on or make changes to this bug.