with multiple-monitors, firefox menus/url history/tooltips shows up on wrong monitor

[Adam Plumb]

Binary package hint: firefox

I have a dual-monitor setup using an NVIDIA 7600GT and proprietary drivers on TwinView mode.

I'm using Intrepid Ibex (8.10) with the latest updates as of Nov 7th.

When I have firefox on the right-side monitor, the menus, url history, textfield history, and tooltips all show up on the left-side monitor.

===============================================

TO REPRODUCE:

1. Have only a single monitor enabled.
2. Open firefox
3. Enable the secondary monitor.
4. Move the firefox window to the secondary monitor.
5. Open menus/tooltips/etc. They will show up on the primary monitor.

WORKAROUND:

To get around this, switch steps 2 and 3.

==============================================

Unfortunately, I can't seem to get a screenshots of the menus/url history/textfield issues because they disappear when I click away from the browser (screenshot won't get taken unless I click away from the menu/history). But I was able to get a shot of a tooltip showing up incorrectly.

[Elig (elig)]

(It may be more obvious if you add a step 5, of adding more bookmarks to your
Bookmarks menu, and noting that they don't appear.)

[Mikepinkerton (mikepinkerton)]

danm owns screen object....i suspect this would happen on macOS as well, but i
don't know for sure.

[Bugzilla-iwaruna (bugzilla-iwaruna)]

eli, if this does *not* refer to Bookmarks off the toolbar, feel free to bounce
it back to me.

[Elig (elig)]

Actually, it also involves the Bookmarks menu (from the menu bar). QA Assigning
back to Sarah, per Claudius's okay.

[Elig (elig)]

Corrected bug summary.

[Trudelle (trudelle)]

Mass moving M17 bugs to M18

[Trudelle (trudelle)]

mass-moving all bugs to m21 that are not dofood+, or nsbeta2+

[Bugzilla-iwaruna (bugzilla-iwaruna)]

*spam*: transferring current XP Menu bugs over to jrgm, the new component owner.
feel free to add me to the cc list (unless am the Reporter) of any of these, if
you have any questions/etc.

[Brade (brade)]

The following is reported by Shawn Broughton on 11/15/2000 at
http://www.macintouch.com/netscape6.html:

The first is a PowerCenter Pro 210 with a Rage Orion card. It's unbearably slow,
but oddly, it always draws popup menus on my second monitor, which is attatched
to the OEM Rage Iic card.

[Mikepinkerton (mikepinkerton)]

how are the monitors oriented? which one is the main monitor? all popups?
context menus too? what about tooltips?

I need more information here.

[Sfraser-bugs (sfraser-bugs)]

Is this the negative coordinates problem?

[Saari (saari)]

Could be, but I think popups go through the same negative coordiate munging code
as all windows.

[Kmcclusk (kmcclusk)]

Hello, my name is Brad Maness and i use Mozilla, for mild web deveolpment, to
get ready for Javascript 1.5 and DOM compliance. Currently i'm using M18 [
Build2000101014 ] and i've run into some problems. I've created my own "property
viewer" for objects, to help me develop a few things, which currently [ though
probably not enough for public use ] works with M18, and this is what i found out.

I started with a 1024x768 resolution and ran the prop. viewer on the [
window.screen ] object and this is what i got :

- window.screen.top = 0
- window.screen.left = 0
- window.screen.width = 1024
- window.screen.height = 768
- window.screen.pixelDepth = 16
- window.screen.colorDepth = 16
- window.screen.availWidth = 1024
- window.screen.availHeight = 740
- window.screen.availLeft = 0
- window.screen.availTop = 0

Then, i minimized all windows, changed the screen resolution to 640x480, and ran
the prop view on the same obj. [ window.screen ]
and this is my output :

- window.screen.top = 0
- window.screen.left = 0
- window.screen.width = 1024
- window.screen.height = 768
- window.screen.pixelDepth = 16
- window.screen.colorDepth = 16
- window.screen.availWidth = 1024
- window.screen.availHeight = 740
- window.screen.availLeft = 0
- window.screen.availTop = 0

None of the vaules updated when i changed the screen resolution. Height, width,
available values, nothing. The only way i was able to get the correct values of
the screen resolution, was if i opened a new Mozilla window and loaded the prop
viewer again on that obj.

[Kmcclusk (kmcclusk)]

I confirmed that window.screen does not return the correct values in Netscape
6.0 on WINNT when the screen size/depth is changed while N6 is running.

[Kmcclusk (kmcclusk)]

The problem is the DeviceContext held by the presentation context is not updated
when the depth changes.

See ScreenImpl::GetDeviceContext

nsIDeviceContext* ScreenImpl::GetDeviceContext()
{

   if(!mDocShell)
      return nsnull;

 nsCOMPtr<nsIContentViewer> contentViewer;
   mDocShell->GetContentViewer(getter_AddRefs(contentViewer));

   nsCOMPtr<nsIDocumentViewer> docViewer(do_QueryInterface(contentViewer));
   if(!docViewer)
      return nsnull;

   nsCOMPtr<nsIPresContext> presContext;
   docViewer->GetPresContext(*getter_AddRefs(presContext));

 nsIDeviceContext* context = nsnull;
   if(presContext)
      presContext->GetDeviceContext(&context);

   return context;
}

Reassigning to myself

[Mikepinkerton (mikepinkerton)]

not much i can do with this w/out more info. futuring.

[Kmcclusk (kmcclusk)]

Setting milestone to mozilla1.0

[Kmcclusk (kmcclusk)]

Clearing milestone.

[Kmcclusk (kmcclusk)]

Setting milestone to future.

[Jst (jst)]

*** Bug 73961 has been marked as a duplicate of this bug. ***

[Spam-minneboken (spam-minneboken)]

*** Bug 118340 has been marked as a duplicate of this bug. ***

[Kmcclusk (kmcclusk)]

Build moving all existing future-P3 bugs to future-P4.

[Mstockman (mstockman)]

I can add some additional info, from using Mozilla (build ID 2002030508, OS X)
on my Titanium Powerbook LCD (Monitor 2, on the right) with an external monitor
attached and configured as the "main" screen (Monitor 1, on the left).

If I open, say, the Bookmarks window (or a browser window, for that matter), and
the left side of the window is within about 300 +/- pixels of the right-hand
edge of monitor 1, right-clicking a bookmark results in the pop-up menu
appearing on monitor 2. If I nudge the bookmarks window left, the pop-up opens
under the mouse pointer, where it should. The window does *not* extend in any
way into monitor 2.

This happens regardless of the size of the window -- it depends entirely on
where the *left* edge of the window is.

This bug is kind of annoying, because it gives the impression that the pop-up
isn't opening at all, until you realize that it's opening several inches and a
monitor away...

Let me know if I can add any more info.

[Tuukka Tolvanen (sp3000)]

*** Bug 135953 has been marked as a duplicate of this bug. ***

[Tuukka Tolvanen (sp3000)]

is this dup/dep bug 62395?

[Pschwartau (pschwartau)]

*** Bug 133483 has been marked as a duplicate of this bug. ***

[Spam-minneboken (spam-minneboken)]

*** Bug 148571 has been marked as a duplicate of this bug. ***

[Spam-minneboken (spam-minneboken)]

*** Bug 136030 has been marked as a duplicate of this bug. ***

[Mgabriel (mgabriel)]

no problem with our matrox cards when using dual head.

[Mstockman (mstockman)]

Just to follow up, this bug still occurs in the 1.0 release.

[Spam-minneboken (spam-minneboken)]

*** Bug 150213 has been marked as a duplicate of this bug. ***

[Spam-minneboken (spam-minneboken)]

*** Bug 154591 has been marked as a duplicate of this bug. ***

[James-freelancepropaganda (james-freelancepropaganda)]

Reproduced this on Chimera OS X build 2002112204 (24 Nov 2002) at this page

http://www.t-mobile.com/locator.asp?referer=/products/overview.asp?phoneid=163904
(one time cookie selector)

If the window is either:
1. Split across the screens (not important)
2. Fully maximised on the monitor. (perhaps the way the windows are drawn this
fully maximised actually extends onto the other monitor (I think I can see a
shadow there ...)) (Possible quirk of Acqa on OS X?)

Then the pop-up shows up off to the left of the window. I've noticed this with
a few other pages as well.

Pismo powerbook with external monitor (extended desktop) as secondary on the
left. If I swap the monitors I get the same behaviour (ie it does not seem to
be related to primary or secondary monitors).

[Spam-minneboken (spam-minneboken)]

*** Bug 180310 has been marked as a duplicate of this bug. ***

[Bzbarsky (bzbarsky)]

*** Bug 182991 has been marked as a duplicate of this bug. ***

[Bzbarsky (bzbarsky)]

*** Bug 184459 has been marked as a duplicate of this bug. ***

[Bugzilla-gtalbot (bugzilla-gtalbot)]

Let's say I have a scr. res. of 1024x768 with the following values:

screen.top = 0
screen.left = 0
screen.availTop = 270
screen.availLeft = 60

and then I change the scr. res. to 640x480.
What are the current values with such scr. res.? What should be the current values?

I would be appreciative of an answer.

[Bzbarsky (bzbarsky)]

*** Bug 186551 has been marked as a duplicate of this bug. ***

[Spam-minneboken (spam-minneboken)]

*** Bug 155717 has been marked as a duplicate of this bug. ***

[Bzbarsky (bzbarsky)]

*** Bug 195971 has been marked as a duplicate of this bug. ***

[David Fraser (davidf)]

I get this on Linux (Ubuntu 8.04) when adding an extra monitor using xrandr.
As to bug 62395, in this case window.screen still shows the resolution of the original screen, not the combined resolution.
Changing OS to All as a result.
There's an upstream Ubuntu bug at https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/229298

See also bug 239043 which had some comments relating to this.

[David Fraser (davidf)]

(In reply to comment #45)
> Note that only on multiple-monitor systems are we apparently prepared to take
> the perf hit of not caching the screen dimensions (in that case simply dragging
> the window from one screen to the other will update the window.screen values).

On Linux (Ubuntu 8.04, Firefox 3), using xrandr to add another screen does not update window.screen properties. So the system can start out being a single-monitor one but change to be multi-monitor, and in this case we should throw out the cache.

See also bug 29100 which is triggered by this, and the related upstream Ubuntu bug at https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/229298

[Adam Plumb (adamplumb)]

Binary package hint: firefox

I have a dual-monitor setup using an NVIDIA 7600GT and proprietary drivers on TwinView mode.

I'm using Intrepid Ibex (8.10) with the latest updates as of Nov 7th.

When I have firefox on the right-side monitor, the menus, url history, textfield history, and tooltips all show up on the left-side monitor.

Unfortunately, I can't seem to get a screenshots of the menus/url history/textfield issues because they disappear when I click away from the browser (screenshot won't get taken unless I click away from the menu/history). But I was able to get a shot of a tooltip showing up incorrectly.

[chadwik (chadwik)]

Marking this as confirmed by bug 243319.

[Adam Plumb (adamplumb)]

With the latest firefox update from this morning (to 3.0.4) this issue is fixed for me. My tooltips/menus all show up in their correct place on the secondary monitor.

[chadwik (chadwik)]

Marking this as fixed

[Adam Plumb (adamplumb)]

I came across this issue again this morning, and thought I had been mistaken when I had reported it fixed. This bug still occurs under the corner case where only a single monitor is enabled, and with firefox open, a second monitor is enabled. If firefox is closed before enabling the second monitor it'll work fine. It must be something that is happening when firefox is opened.

Here's how I reproduce it:

1. Have only a single monitor enabled.
2. Open firefox
3. Enable the secondary monitor.
4. Move the firefox window to the secondary monitor.
5. Open menus/tooltips/etc. They will show up on the primary monitor.

To get around this, switch steps 2 and 3.

[Martin Capitanio (capnm)]

...
> 1. Have only a single monitor enabled.
> 2. Open firefox
> 3. Enable the secondary monitor.
> 4. Move the firefox window to the secondary monitor.
> 5. Open menus/tooltips/etc. They will show up on the primary monitor.

2+ more multi-monitor related long standing "gnome disagrees
with the x11 driver about the monitor order" bugs:

* Have only a single (the internal LVDS notebook) monitor enabled.
* Have a drawer placed on the gnome panel.

* Plug the second monitor, everything looks sane so far:

#xrandr
Screen 0: minimum 320 x 200, current 1280 x 800, maximum 2960 x 1850
VGA connected (normal left inverted right x axis y axis)
   1680x1050 59.9 + 60.0
...
LVDS connected 1280x800+0+0 (normal left inverted right x axis y axis)
331mm x 207mm
   1280x800 60.0*+
...

* Enable the secondary monitor
(e.g. xrandr --output VGA --right-of LVDS --mode 1680x1050).

[1] Both top and bottom gnome panels perform an immediately
jump to the external secondary monitor.

* Don't let it get you down, unlock and drag the panels back to the
primary monitor.

* Click on the drawer on primary monitor.

[2] The the drawer content pops up on secondary monitor.

[+] Almost every splash-window appears horizontal in the middle between
both monitors.

[+] Most OpenGL games smashes a 2 monitor geometry setting so badly,
that the only option left is restart the x11 server.

[Chris Bainbridge (chris-bainbridge)]

Happens under Ubuntu Intrepid and Firefox 3.0.5. It is very easy to reproduce:

xrandr --output VGA-0 --off
firefox &
xrandr --output VGA-0 --mode 1280x1024
xrandr --output VGA-0 --right-of LVDS

I.e. start firefox with only a single display active, enable second display to right of original display, move firefox window to the new display, and click on "Help". Popup will appear on left display.

Firefox seems to be the only application that gets this wrong.

[Chris Bainbridge (chris-bainbridge)]

Possibly related to https://bugzilla.mozilla.org/show_bug.cgi?id=62395 and https://bugzilla.mozilla.org/show_bug.cgi?id=29100

[Chris Bainbridge (chris-bainbridge)]

This bug has also been reported in Launchpad https://bugs.launchpad.net/firefox/+bug/295192

[Chris Bainbridge (chris-bainbridge)]

I just tried building firefox from the latest Mercurial sources (version says 3.2a1pre) and this bug appears to be fixed.

Build instructions here: https://developer.mozilla.org/En/Simple_build
Configure options were: ../configure --enable-debug --disable-optimize --enable-application=browser --disable-crashreporter

I tried both with and without --enable-xinerama and saw no difference - the configure script doesn't seem to check for this option, so I'm wondering whether it even makes a difference anymore?

Since the build options of firefox no doubt vary across platforms it would be useful if someone else could test and confirm that this will no longer be an issue in firefox-3.2.

[Chris Bainbridge (chris-bainbridge)]

I ran in to bug #61000 which is possibly a dupe of this one. With the latest firefox sources from Mercurial (apparently 3.2a1pre) I no longer see either this bug (bookmark window size now adapts to change in resolution), or bug #61000 (popup windows now appears on correct monitor).

It would be useful if someone else could check to make sure 3.2a1pre does indeed fix this issue. Hey, almost 9 years for a fix...

[Chris Bainbridge (chris-bainbridge)]

I just tried building firefox from the latest Mercurial sources (version says 3.2a1pre) and this bug appears to be fixed.

Build instructions here: https://developer.mozilla.org/En/Simple_build
Configure options were: ../configure --enable-debug --disable-optimize --enable-application=browser --disable-crashreporter

I tried both with and without --enable-xinerama and saw no difference - the configure script doesn't seem to check for this option, so I'm wondering whether it even makes a difference anymore?

Since the build options of firefox no doubt vary across platforms it would be useful if someone else could test and confirm that this will no longer be an issue in firefox-3.2.

[Sesquile (sesquile)]

*** Bug 471894 has been marked as a duplicate of this bug. ***

[Bourdieu (mathieu-bouillaguet)]

I can confirm that the problem is fixed with firefox 3.1 beta 2 on linux.

[LogicDaemon (logicdaemon)]

got like this problems under Windows in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b4pre) Gecko/20090410 Shiretoko/3.5b4pre ID:20090410053901

e.g. when browser window is on second screen,
- all (!) pop-up menus appear on first one, including address bar and search auto-complete, right-click and application main menu
- mouse middle-button "scroll" cursor appears on first screen

next will be screenshots

[LogicDaemon (logicdaemon)]

http://www.imagefilez.com/out.php/i352875_mousescrollindicator.png
http://www.imagefilez.com/show.php/352875_mousescrollindicator.png.html

http://www.imagefilez.com/out.php/i352874_menutools.png
http://www.imagefilez.com/show.php/352874_menutools.png.html

http://www.imagefilez.com/out.php/i352873_menutextareacontext.png
http://www.imagefilez.com/show.php/352873_menutextareacontext.png.html

http://www.imagefilez.com/out.php/i352872_menufile.png
http://www.imagefilez.com/show.php/352872_menufile.png.html

[Marius Gedminas (mgedmin)]

It's worse than that. When the primary screen is not at the top-left corner of the virtual desktop, popup menus (including the awesomebar) may appear partially or completely off-screen.

Here's an ASCII-art diagram:

       +----+
       | 2 |
  +----| |
  | 1 | |
  +----+----+

1 is the internal screen, 2 is the external screen. Firefox appears to use the dimensions of screen (1) to limit the area of its popups, but it assumes that that area starts at the top-left corner.

Platform: Linux, using RandR 1.3.

[Patricio (patricio-stwing)]

I have this problem too. Firefox 3.0.10 menus open in a different monitor in Jaunty.

[dvhart (darren-dvhart)]

Does anyone have a firefox 3.2* package they could make available on a ppa?

[Chris Bainbridge (chris-bainbridge)]

https://launchpad.net/~fta/+archive/ppa

I haven't tried it though.

[Andreas Jonsson (sonofjon)]

I can confirm this bug on an up-to-date Jaunty installation. Not surprisingly this bug also affects Mozilla Thunderbird.The workaround suggested by the OP works.

[Adam Plumb (adamplumb)]

I've upgraded my firefox-3.0.x installation to the PPA's 3.5.4pre version and this behavior appears to be fixed. Hopefully someone else can do the upgrade and confirm that.

[Vseerror (vseerror)]

still see this?

[Chris Bainbridge (chris-bainbridge)]

> still see this?

I don't' have a second monitor to test this now. As I said in Comment 20, it should be easy to retest - use xrandr to disable a display, start firefox, use xrandr to re-enable the display, drag firefox window to that display, click "help".

[Marius Gedminas (mgedmin)]

I cannot reproduce this bug any more with Firefox 28.0, nor with 31.0a1.

Things I tested:
1. Started Firefox in a dual-head configuration like I ASCII-art'ed in comment 27, moved it around to the left and right monitors and tried to open right-click popup menus in various positions. The menu always appeared on the same screen as the Firefox window and was always entirely visible. Same with the awesomebar popup.

2. Closed Firefox, unplugged external display cable, started Firefox, tested the right-click menu once, then plugged in the cable after FF was already running and repeated my tests from #1. Same result: things work fine.

[Michael Jastram (jastram)]

I used to see this, but cannot reproduce it any more either.

[Chris Bainbridge (chris-bainbridge)]

> still see this?

I do not see this on Gnome or Unity. I do see it on XFCE in Debian Testing (jessie), both with the firefox binary from mozilla, and the iceweasel binary from Debian.

[Chris Bainbridge (chris-bainbridge)]

btw the subject of this bug needs updating - my hardware setup is Intel HD graphics with triple portrait monitors.

[Chris Bainbridge (chris-bainbridge)]

To reproduce this: run XFCE, put Firefox on the left monitor (or maybe centre for triplehead), maximise firefox window, then right click on the right side of the Firefox window. The popup will appear on the monitor to the right. Tested with Debian Testing and Firefox 29 beta (and Iceweasel).

[Chris Bainbridge (chris-bainbridge)]

Update: I just retried this on Gnome (Debian Testing) and the bug also occurs there. Same method to reproduce as in comment #33. Using other apps eg. chromium was ok (right-click popup stays on same monitor).

[Chris Bainbridge (chris-bainbridge)]

Created attachment 8414413
firefoxbug-gnome.png

This is a screenshot demonstrating the bug on a triple monitor setup with the latest version of Firefox beta from mozilla.org running on Gnome (Debian Testing).

[Stijn+bugs (stijn+bugs)]

Created attachment 8565782
Screenshot of save password popup in KDE5

[Stijn+bugs (stijn+bugs)]

Created attachment 8565783
Screenshot of form history popup in KDE5

[Stijn+bugs (stijn+bugs)]

I've added a couple of screenshots showing this problem in Firefox on KDE5. This is on Gentoo using the proprietary nvidia driver, so this really doesn't seem driver or desktop environment related.

And I am seeing the same problem in Thunderbird too, e.g. with the popup showing addresses from addressbook when I start typing an address in the To field.

[dino99 (9d9)]

outdated flavor, report about a newer active version if needed

[medb (medb)]

Still reproducible on Ubuntu 15.10 Alpha 2 and Firefox 39.0

[bymoz089 (kyv-66tsaypfp4rf)]

I tracked it down somewhat:

if you change the value:
"layout.css.devPixelsPerPx"
in "about:config"
to something else than "-1", "0" or "1"
eg.: use "0.8"
then you encounter the problem with misplaced menus
this is reproduceable and really annoying.