Opened 8 years ago
Closed 8 years ago
#10759 closed bug (invalid)
Mouseout event behaviour differs from 1.6.4 to 1.7
| Reported by: | anonymous | Owned by: | anonymous |
|---|---|---|---|
| Priority: | undecided | Milestone: | None |
| Component: | unfiled | Version: | 1.7 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
See jsFiddle - http://jsfiddle.net/9Va8V/2/
It works in 1.6.4 but breaks in 1.7 unless I remove "mouseout" event.
Change History (3)
comment:1 follow-up: 2 Changed 8 years ago by
| Owner: | set to anonymous |
|---|---|
| Status: | new → pending |
comment:2 Changed 8 years ago by
| Status: | pending → new |
|---|
Replying to dmethvin:
Can you tell me why the mouseout is there? I don't think it should be.
Good question - think it was out of (bad) habit! However it is interesting that it doesn't work in 1.7 whilst it worked in 1.6.4. Replacing "focus" with "mouseover" - http://jsfiddle.net/9Va8V/3/ - made it all work again. Could it be that it was a bug in 1.6.4 but "fixed" in 1.7? I am unable to find anything regarding mouseout in the bug tracker.
Perhaps worth adding a note in the documentation about mouseout needing mouseover?
comment:3 Changed 8 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
There was a bug in pre-1.7 versions where mouseover/mouseenter and mouseout/mousleave could interfere with each other when attached to the same event, depending on the order where the events were attached. I can't find the ticket atm but I remember fixing it. This code may have been trying to work around that bug. However, I think the correct code should not have mouseout there since it will fire when the pointer leaves the li into the a.
Can you tell me why the mouseout is there? I don't think it should be.