Closed Bug 207718 Opened 22 years ago Closed 20 years ago

Mouseout being triggered when mouse stops moving.

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: ezjosh, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030529 The mouseout event is being triggered when the mouse cursor is no longer moving. This occurs on all web pages and the Mozilla UI. This issue started when I installed a Microsoft keyboard, this one (http://www.microsoft.com/hardware/keyboard/nmmk_info.asp) to be exact. A "Natural MultiMedia Keyboard". Reproducible: Always Steps to Reproduce: 1. Start Mozilla. 2. Move the mouse over a mouseover object. (button, link, etc...) 3. Halt all mouse movement. Actual Results: The mouseout event is triggered. Expected Results: Mouseout should only be triggered when the mouse leaves and is no longer above the object. I also use a "IntelliMouse Explorer" (http://www.microsoft.com/hardware/mouse/ie_info.asp) as my pointing device. As of this date, I have installed all known system upgrades. Including Mozilla 1.4 RC, to ensure this bug still exists. This bug makes is difficult, and sometimes annoying, when trying to navigate mouse based menus on websites. Usually Javascript or Java based. This issue is also seen in the Mozilla UI as well.
This only occurs on the second monitor. Where the second monitor is to the left of the primary monitor.
I have the same problem. I am using Windows XP on a Toshiba Tecra 8100 with a SavageMX video card. I also have a microsoft mouse and keyboard. This bug occurs in both Mozilla 1.3 and 1.4. And this bug occurs only on the second monitor (which is to the left of the primary). The mouseout event makes it nearly impossible to open submenus because the menus will disappear as soon as the mouse stops moving.
Reporter: although I doubt it will fix anything (this issue is pretty specific, and I can't test it) - could you try with a recent nightly build just to see if it still happens ? Thanks!
Product: Browser → Seamonkey
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.