Closed
Bug 230512
Opened 22 years ago
Closed 22 years ago
multiple monitors mouse-over failure with negative coordinates
Categories
(Core :: XUL, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 135079
People
(Reporter: jeffh, Assigned: jag+mozilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Firebird/0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Firebird/0.7
I have an XP dual monitor setup where the right monitor is my "primary" monitor,
and thus the left monitor is in a space that is essentially negative coordinate
space of the primary monitor. To draw this out, Display Properties -> Settings
shows:
_____ _____
| | | |
| 2 | | 1 |
----- -----
and the Secondary Display has coords [-1600..0).
When I have a mozilla-based app (Firebird, Thunderbird, Komodo) on the negative
monitor, all mouse-over operations all fail. This includes toolbar button
highlighting, tabnotebook page highlighting, tooltips, statusbar changes (on
links and things) and implicit menu expansion. The entering of an item is
recognized, but then is immediately lost again (so you get just a flash of the
correct operation). You don't realize how much mouse-over behaviors add to the
UI experience until you don't get them anymore ...
Simply moving the app into the positive coord space (primary monitor) makes
everything work. If I switch around so that the extra monitor is also in
positive coord space, that also works.
I have only verified this on WinXP, but it may be an issue if similar multiple
monitor setups can be created on X and/or the Mac.
Reproducible: Always
Steps to Reproduce:
1. Set up monitors as noted above
2. Run mozilla-based app, place it in monitor 2.
3. Note broken mouse-over behavior.
Actual Results:
Broken mouse-over behavior.
Expected Results:
Worked.
Comment 1•22 years ago
|
||
*** This bug has been marked as a duplicate of 135079 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•