W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2010

Re: Clarification on mouseenter/mouseleave

From: Sean Hogan <shogun70@westnet.com.au>
Date: Thu, 01 Jul 2010 11:19:37 +1000
Message-ID: <4C2BED29.4030605@westnet.com.au>
To: Joćo Eiras <joao.eiras@gmail.com>
CC: "www-dom@w3.org" <www-dom@w3.org>
  On 1/07/10 11:14 AM, Joćo Eiras wrote:
> On , Sean Hogan <shogun70@westnet.com.au> wrote:
>
>>   On 29/06/10 11:08 AM, Joćo Eiras wrote:
>>> After further review I got confused. IE does set the target to the
>>> inner element, it fires the listeners on both the inner element and
>>> outer element, but doesn't bubble up to the body.
>>> Does this mean that the user agent has to fire an event for each node
>>> that is unhovered, each one with their separate capturing phases ?
>>>
>>>
>>>
>>
>> Looks like it.
>> And the W3C DOM model won't haven't an equivalent to fromElement - for
>> mouseleave - and toElement - for mouseenter. I can't see a need for
>> them, but would be nice to know how they are being used on the web.
>>
>
> There is, it's relatedTarget.
>

For mouseleave, relatedTarget is equivalent to toElement.
For mouseenter, relatedTarget is equivalent to fromElement.
Received on Thursday, 1 July 2010 01:20:24 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:04 GMT