Closed Bug 242858 Opened 21 years ago Closed 20 years ago

Context, drop-down menus appear in wrong location when running Firefox on second monitor in Windows XP

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 98830

People

(Reporter: beltzner, Assigned: bugzilla)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8 StumbleUpon/1.908 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040206 Firefox/0.8 StumbleUpon/1.908 nb: This seems to be related to <a href="http://bugzilla.mozilla.org/show_bug.cgi?id=242181">bug 242181</a>. When Firefox 0.8 is running in a second monitor using Windows XP (SP1), I have found that both context and drop-down menus consistently appear in unexpected locations. If the second monitor is to the LEFT of the primary monitor, then menus usually appear at the leftmost edge of the primary monitor. If the second monitor is to the RIGHT of the primary, then menus appear at the rightmost edge of the primary, and bleed onto the secondary. Reproducible: Always Steps to Reproduce: 1. Plug in a second monitor to your PC or laptop 2. Through WinXP's display settings, select "extend my windows desktop onto this monitor" 3. Launch Firefox, and drag it onto the secondary monitor. 4. Right-click on a tab, link or page, or select a drop-down menu. Actual Results: Menus appeared either entirely or partially on the primary monitor. Expected Results: Menus should have appeared at location of mouse-click (Right now I'm using the Smoke theme -- I'll reboot the browser in the standard theme to check.)
UPDATE: It's not dependant on the theme, but it *is* dependant on when the browser is launched. The bug only shows up when Firefox is running *before* one enables the multiple-monitor feature in XP ... if Firefox is closed when the multiple monitors feature is turned on, subsequently launched Firefox processes work fine. Please amend the reproducing steps above to: Reproducible: Always Steps to Reproduce: 1. Launch Firefox 2. Plug in a second monitor to your PC or laptop 3. In WinXP's settings, select "extend my windows desktop onto this monitor" 4. Drag Firefox onto the secondary monitor 4. Right-click on a tab, link or page, or select a drop-down menu.
*** This bug has been marked as a duplicate of 135079 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
v.
Status: RESOLVED → VERIFIED
Mike Beltzner, can you confirm that this bug has been fixed (per bug 135079)? if it hasn't, this is most likely another issue that has a few dupes (see bug 243518 and bug 249851).
*** Bug 243518 has been marked as a duplicate of this bug. ***
*** Bug 249851 has been marked as a duplicate of this bug. ***
Nope. Doesn't seem to be fixed. Using the steps I provided in comment #1 (http://bugzilla.mozilla.org/show_bug.cgi?id=242858#c1), I still get the same inappropriate behaviour for drop-down menus and context-menus in Firefox 0.9.2 Do note, however, that the Mozilla patch was apparently landed after Firefox branched off the 1.7 trunk ... or something. I think that's what happened. I'm new to a lot of this, and trying to decypher the comments :) In the meantime, since it's still *there* and all, I'll reopen this bug.
Status: VERIFIED → UNCONFIRMED
Resolution: DUPLICATE → ---
Reproduces like a charm. By the way, I wonder if Bugzilla shouldn't automatically confirm an unconfirmed bug that's a dup of a confirmed bug...
Status: UNCONFIRMED → NEW
Ever confirmed: true
this happens on os x 10.3.4 as well, (firefox v0.9.1) checked positive and negative second monitor space and it doesn't seem to matter what position the second monitor is on, it still places the context menus and other items like addres bar auto fill on the primary monitor.
Please reopen if you disagree that this is not a dupe. *** This bug has been marked as a duplicate of 98830 ***
Status: NEW → RESOLVED
Closed: 21 years ago20 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.