open context menu doesn't use just one screen in dual screen setup

RESOLVED INCOMPLETE

Status

()

Core
XUL
RESOLVED INCOMPLETE
14 years ago
8 years ago

People

(Reporter: Ysre, Unassigned)

Tracking

1.7 Branch
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [closeme 2010-09-15])

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040122 Debian/1.6-1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040122 Debian/1.6-1

When maximizing the Mozilla window  it only maximizes to one screen of a dual
screen setup (like it should).
When opening a context menu anywhere near the border between the two screens in
a dualheaded X11 setup  the context menu will use both screens (one part being
where you clicked, the other part on the second screen).

This happens with _all_ context menus AFAIK.

I don't know if this is a mozilla bug per-se or just a problem of an underlying
library..
Anyhow: Why does Mozilla use only one screen when maximizing, but not when a
context menu is displayed?
The context menu should stay on the screen where the Mozilla window is.

Sounds like something Mozilla-specific (although not very specific.. I know this :))
Well someone with more knowledge than me will surely know :)


Reproducible: Always
Steps to Reproduce:
1. right click on any context-menu enabled element near the border of the screen
where mozilla resides (as in "when you maximize mozilla  it gets blown up to the
screen it resides on.. not both screens")
2. see the context menu split over the two screens


Actual Results:  
the context menu uses two screens although the mozilla window does only use one.

Expected Results:  
the context menu should stay on the screen that mozilla chose to use (eg. the
one it maximizes to).

Comment 1

14 years ago
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050225
Firefox/1.0.1
Used on PC, Graphic device ATI Mobility Radeon 7500, Windows XP Pro

Ok I know this bug was committed for the Linux OS but since they allways tell us
to look for a bug covering the same problem I'm writing here.

Im using Windows XP with a Desktop covering two displays connected to my
graphics device.

I can sucessfully move and use Firefox on the second screen of the desktop by
dragging it out of the frist one to the right. Maximise will then actually
maximise the window to the second screen.
But every time I click to open a menu either in the main menu, a contextual menu
or a combobox. The menu will display entirely on screen one (allways to the very
right) instead of the place where I clicked the menu on screen 2.
For Thunderbird it's exactly the same.

Comment 2

13 years ago
I have the same problem although it doesn't occur always.

When I boot my computer (Windows XP Professional SP2) with the VGA connector
already plugged in (so when the dual screen is activated on boot) everything
works fine.

But when I activate dual screen with Windows XP already running, I get all the
popup menu's etc on my primary screen although FireFox is running maximized on
the second screen.
Assignee: hyatt → nobody
QA Contact: shrir → xptoolkit.menus

Updated

10 years ago
Component: XP Toolkit/Widgets: Menus → XUL
QA Contact: xptoolkit.menus → xptoolkit.widgets

Comment 3

10 years ago
Re comment #1 and Comment #2 - these are actually bug 29100, this bug is different.

Comment 4

8 years ago
Ysre, do you still see this issue in version 3.6?
Whiteboard: [closeme 2010-09-15]

Comment 5

8 years ago
Closing since now after whiteboard closeme date and no reply to last comment.

Please reopen/comment with further info, if you still see this issue with Firefox 3.6.13 or later in safe mode:
http://support.mozilla.com/kb/Safe+Mode

If you wish, you can also try to reproduce in Firefox 4 Beta 8 or later:
http://www.mozilla.com/en-US/firefox/all-beta.html
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
Version: Trunk → 1.7 Branch
You need to log in before you can comment on or make changes to this bug.