236614 - Mouse hover fails in negative coords on extended desktop

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[Brian]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

I have extended my Windows XP desktop to a second monitor. The second monitor is
positioned higher than the first so that its upper portion's Y position in
negative. Like so:
           +--------+
           |////////|  <- Bad area!
+--------+ |    2   |
|        | +--------+
|    1   |
+--------+

When Mozilla is in the 2nd window, any thing that reacts to a mouse hover (e.g.
hyperlinks, browser buttons) misbehaves when it is in the portion of the screen
that is higher than the top of screen 1. The bad behavior is that the hover
effect occurs but then disappears after 1/2 second or so. This behavior does not
happen in the portion of screen 2 that is below the top of screen 1.

Reproducible: Always
Steps to Reproduce:
1. Extend desktop to a 2nd monitor.
2. Set the 2nd screen higher than the first.
3. Open Mozilla in screen 2 and position it in the upper portion.
4. Move the mouse over any element of Mozilla's toolbar (e.g. the Refresh button).

Actual Results:  
The element (e.g. the button) changes color but immediately reverts to its
unselected state.

Expected Results:  
Kept the selected mouse-hover state for the element.

Comment 1

[mozilla-bugs]

Mozilla 1.6 - Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) 
Gecko/20040113
Firefox 0.8 - Mozilla/5.0 (Windows; U; Windows NT 5.1; de-DE; rv:1.6) 
Gecko/20040206 Firefox/0.8

Same Problem here. I've reproduced this bug with negative X-Coordinates
Screen Setup:
     +---------+
     |         |
     |    1    |
     +---------+
+--------+
|////    |
|////2   |
+--------+
  ^-- Area where hover/onmouseover/onmouseout misbehave

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.