Open
Bug 252249
Opened 22 years ago
Updated 3 years ago
onmouseover event-handler is not executed and mouse pointer style is not updated
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: norbert.notz, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a3) Gecko/20040718 Firefox/0.9.1+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a3) Gecko/20040718 Firefox/0.9.1+
Bug 195045 seems to be fixed in recent Firefox nightlies.
But a similar problem still remains, that can be reproduced in three different ways:
1.
- open two tabs, at least one should include a website with links
- switch to a tab with a site that contains links and place the mouse pointer of
a link
- press CTRL+TAB to switch to another tab and do _not_ move the mouse!:
The hand-style of the pointer remains also it is not over a link anymore.
2. alternative steps to reproduce:
- open a second Firefox window
- place the pointer over a link
- press ALT+F4 to close the window and do _not_ move the mouse:
The pointer no also keeps hand-style!
3. alternative steps to reproduce
- open the following website for example:
http://www.assmann.com/htdoc/germany/products/components-heatsinks.htm
- click one of the 3 images: This opens a new window containg a big picture.
- place the mouse pointer over this picture: The pointer becomes hand-style.
- click the left mouse button and do _not_ move the mouse!:
The mouse pointer still has hand-style, although it is not placed over a link
anymore!
Reproducible: Always
Steps to Reproduce:
I found out that also onmouseover event-handlers are not executed when doing as
described here. I think this is caused by the same bug as the mouse pointer
style update problem. So I add this as comment here instead of submitting as
another bug:
- open a site that has some onmouseover-effects. For example simple text links
that change colors if you move the mouse cursor over it.
- press CTRL+t to open a new tab (while NOT moving the mouse!)
- press CTRL+TAB to switch back to the page with the onmouseover effect:
You have to move the mouse a bit to have the onmouseover-effect executed!!
Further on I found a similar problem with layers: If a layer that contains
onmouseover-effects (for example also such a link that changes its color) opens
under the mouse pointer, the mouse has to be moved a bit to have the
onmouseover-effect executed! IE does not have this bug!
In all cases, the event-handler onmouseover (and the mouse pointer style) should
be executed (updated) with no need to move the mouse.
Because of the event-handler bug, I increase severity to major. I hope this is OK.
Severity: normal → major
Summary: mouse pointer style update problem → onmouseover event- handler and mouse pointer style update problem
Summary: onmouseover event- handler and mouse pointer style update problem → onmouseover event-handler is not executed and mouse pointer style is not updated
Another way to reproduce the problem:
- move the mouse pointer over a link (hand-style pointer) or text (cursor-style
pointer)
- press F5 and do not move the mouse:
The mouse pointer has arrow-style, till you move it a bit.
Onmouseover-event is also not executed when doing so. I have tested it with a
link that changes color if the mouse pointer is over it: After F5 the
onmouseover color was removed till I have moved the mouse a bit.
Please also have a look at bug 246786. Maybe it depends on this bug.
In Bug 255863, there is also mentioned a problem with not updated mouse-pointer
styles when dragging a unfocused link quickly.
Assignee: firefox → events
Component: General → Event Handling
Product: Firefox → Browser
QA Contact: firefox.general → ian
Version: unspecified → Trunk
(You have set "Trunk". But I guess it is not a trunk-only problem. But I only
have tested a latest-trunk nightly.)
This bug also is annoying if a magnifying-glass-style pointer is shown to zoom
in/out pictures. So for example after zooming in, a zoom-in ursor is kept. The
mouse has to be moved to update it to zoom-out. (and vice versa)
[since I'm not sure if this bug is correct in event-handling I will change to
"General". I don't know if this is a event-handling only problem, because of
pointer update problem.]
Please note, I don't know if "Trunk" is correct version.
Component: Event Handling → Browser-General
OS: Windows 2000 → Windows XP
Component: Browser-General → General
Product: Browser → Firefox
Version: Trunk → unspecified
Place the mouse pointer over a link, then scroll down with m. wheel(or up down
arrows) - pointer stays hand-styled. Do not move the mouse.
Comment 10•21 years ago
|
||
Could be related to Bug 185293 which also has troubles with mouse events not
registering until the mouse is moved.
Mouse scroll not updating cursor seemed to be fixed in the latest Mozilla
nightly, but since it also decided to eat 100% CPU and other nastiness, I
didn't test further. All described test cases show bug behavior in Mozilla
1.7.5
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217
Comment 11•21 years ago
|
||
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 12•21 years ago
|
||
Everyone posting has been able to reproduce the bug. The problem is that nobody
with confirm privelege has taken time to actually confirm it.
Just for the record, still present in SeaMonkey 1.0a
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050910
SeaMonkey/1.0a
Updated•20 years ago
|
Component: General → Event Handling
Product: Firefox → Core
Version: unspecified → Trunk
Comment 13•20 years ago
|
||
I think this bug will remain UNCO until a testcase page or two is posted as attachments.
Updated•17 years ago
|
Assignee: events → nobody
QA Contact: ian → events
Comment 14•17 years ago
|
||
Another problem relating to this mouse event handling (I am working on v3.0 /win xp).
Testcase... create two pages:
1.html and 2.html
both linking to the other one via such a link (at the exact same document position!):
<a href="#" onmouseover="this.href='2.html'">
Now, if you initially move the mouse to that link, the href attribute is changed. Thus clicking results in opening the other page.
Yet, if you do not move the mouse... this onmouseover event is NOT triggered only until you "wiggle" the mouse for a bit.
I think this bug in all it's flavours should rightfully be called the "wigglebug"... if not the "wiggle policy"?!?
In other words, loading a page, switching a tab to a page, etc... should trigger the mouseover event at the mouse position... at least it does on ie(8) and chrome, but not in opera(9).
| Assignee | ||
Updated•7 years ago
|
Component: Event Handling → User events and focus handling
Comment 15•4 years ago
|
||
In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.
Severity: major → --
You need to log in
before you can comment on or make changes to this bug.
Description
•