Side navigation
#10759 closed bug (invalid)
Opened November 11, 2011 12:11PM UTC
Closed November 11, 2011 02:42PM UTC
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.
Attachments (0)
Change History (3)
Changed November 11, 2011 01:27PM UTC by comment:1
| owner: | → anonymous |
|---|---|
| status: | new → pending |
Changed November 11, 2011 02:19PM UTC by comment:2
| status: | pending → new |
|---|
Replying to [comment:1 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?
Changed November 11, 2011 02:42PM UTC by comment:3
| 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.