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

Re: mouseenter, mouseleave

From: Garrett Smith <dhtmlkitchen@gmail.com>
Date: Fri, 31 Jul 2009 13:40:01 -0700
Message-ID: <c9e12660907311340j76e19a25ucf078c2ccad53819@mail.gmail.com>
To: Martijn <martijn.martijn@gmail.com>
Cc: Maciej Stachowiak <mjs@apple.com>, Jonas Sicking <jonas@sicking.cc>, Jacob Rossi <t-jacobr@microsoft.com>, "www-dom@w3.org" <www-dom@w3.org>, Travis Leithead <travil@microsoft.com>
On Fri, Jul 31, 2009 at 4:26 AM, Martijn<martijn.martijn@gmail.com> wrote:
> On Fri, Jul 31, 2009 at 10:02 AM, Maciej Stachowiak<mjs@apple.com> wrote:
>> On Jul 31, 2009, at 12:26 AM, Garrett Smith wrote:
>>> Isn't that what I just explained 31 minutes prior?
>> I didn't read your message before posting. I suspect many people won't read
>> your message at all, due to your chronic insufferable rudeness. So perhaps
>> those people will find my explanation helpful.
> I couldn't find any rudeness in that message at all.

Neither could I and apparently we were discussing the same thing as no
correction to my explanation was forthcoming.

Mouseleave events are not practical for cross browser development
because they aren't implemented in many browsers. Changing that still
leaves a problem:

How do I detect "onmouseleave" support?

One possibility would be to have a there is a mouseleave property on
the element. That way, its presence could be detected:-

"onmouseleave" in el;

- ideally true

Gecko doesn't do that. For example:-

'onclick' in document.createElement("div");

false in Gecko.

> Btw, I think that mouseenter/mouseleave would also beneficial for
> tooltip handling in Mozilla. There is for instance
> https://bugzilla.mozilla.org/show_bug.cgi?id=301317 which could be
> fixed by using the mouseenter/mouseleave events, I think.

Seems relevant.

> Regards,
> Martijn
>> Regards,
>> Maciej

Received on Friday, 31 July 2009 20:40:41 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:36:55 UTC