- From: Olli Pettay <Olli.Pettay@helsinki.fi>
- Date: Mon, 01 Feb 2010 11:25:11 +0200
- To: Sean Hogan <shogun70@westnet.com.au>
- CC: "www-dom@w3.org" <www-dom@w3.org>
On 2/1/10 4:02 AM, Sean Hogan wrote: > On 1/02/10 10:48 AM, Sean Hogan wrote: >> On 1/02/10 5:21 AM, Olli Pettay wrote: >>> mouseenter and mouseleave >>> - They still need to be defined more precisely. >> >> I think they are supposed to match IE behavior. >> >>> When mouse is moved for body element to >>> <h1><h2><h3>foobar</h3></h2></h1> will there be >>> 3 mouseenter events dispatched? >> >> That isn't valid HTML. But assuming that it is... >> >> It depends. If the mouse move directly to h3 - without moving over h1 >> or h2 - then there will be only one event. >> This could happen if h3 is positioned absolutely (or relatively, or >> floated, etc) or even if the border of h3 coincides with the border of >> h1 and h2 (which it would if margins, borders and paddings are all zero). >> > > Forget that. I was going by memory of some testing I did last year - > either my memory or my testing was faulty. > I just tested again and I think the spec is pretty close to IE behavior > (but agree that it could be worded better). Though, I think the spec is still not clear enough. In which order should the events fire; first to h1 or h3? And what if there are mouseenter listeners in h1/h2/h3 and wherever the event fires first, the listener moves or removes h2. Do the rest of the events still fire? -Olli > > Sorry about that. > Sean > > >
Received on Monday, 1 February 2010 09:25:46 UTC