Bug 17627 - The order of mouseenter/leave events in a subtree should be defined
Summary: The order of mouseenter/leave events in a subtree should be defined
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - DOM3 Events (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Travis Leithead [MSFT]
QA Contact: public-webapps-bugzilla
Keywords: needsReview
Depends on:
Reported: 2012-06-28 09:59 UTC by Olli Pettay
Modified: 2012-08-23 23:17 UTC (History)
4 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Olli Pettay 2012-06-28 09:59:11 UTC
<div id="outer"><div id="middle"><div id="inner">foo</div></div></div>

When you move mouse to over the foo, mouseenter should be dispatched first to
outer, then middle, then inner.
When you move mouse out from foo, mouseleave should be dispatched first to
inner, then middle, then outer.
(That is how IE, Opera and Gecko behave atm)
Comment 1 Travis Leithead [MSFT] 2012-07-30 23:29:59 UTC
Comment 2 Travis Leithead [MSFT] 2012-07-31 00:08:06 UTC
Fixed by adding a 3rd sequence of events and description to section
Comment 3 Andy Harrison 2012-08-01 17:22:06 UTC
Since all three divs have the same dimensions and position, only a single mouseover is dispatched (to inner) when the mouse is moved from outside of the divs to over the foo. I think it should be made clear that mouseenter will then be dispatched to each of outer, middle, and inner (not just inner).
Comment 4 Travis Leithead [MSFT] 2012-08-06 18:26:30 UTC
Ah got it. I assumed no-overlap in my scenario. A picture would be helpful to explain this too. I'll give it a shot.
Comment 5 Travis Leithead [MSFT] 2012-08-23 23:17:04 UTC
Checked in the updated scenario (including an explanatory graphic) into the same section. I think this resolves the bug :-)