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

Re: Please Review mouseover, mouseout, mouseenter, and mouseleave

From: Garrett Smith <dhtmlkitchen@gmail.com>
Date: Thu, 10 Sep 2009 15:20:16 -0700
Message-ID: <c9e12660909101520k49f2f94di9a37678dff73970e@mail.gmail.com>
To: Doug Schepers <schepers@w3.org>
Cc: "www-dom@w3.org" <www-dom@w3.org>
On Thu, Sep 10, 2009 at 2:25 PM, Doug Schepers <schepers@w3.org> wrote:

[snip]

> [1]
> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-mouseevents


| To create an instance of the MouseEvent interface,
| use the DocumentEvent.createEvent("MouseEvent") method call.

The code would be functional if it were to call |createEvent| on an
*instance* of DocumentEvent, and that could be marked up as:

<code><var>document</var>.createEvent("MouseEvent");</code>

| Note: When initializing MouseEvent objects using initMouseEvent
| or initMouseEventNS, implementations should use the client
| coordinates clientX and clientY for calculation of other
| coordinates (such as target coordinates exposed by DOM Level 0
| implementations).

Add:

| ... (such as target coordinates exposed by DOM Level 0
| implementations or other proprietary properties e.g.|pageX|).


I had thought that |canDispatch| was out and I agreed with removing
it. What is the reason for it?

Garrett
Received on Thursday, 10 September 2009 22:20:57 GMT

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