W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2013

Re: [ui-events] MouseEvent details

From: Dimitri Glazkov <dglazkov@chromium.org>
Date: Tue, 12 Feb 2013 09:19:17 -0800
Message-ID: <CADh5Ky20-UR7HShm-R7_Wnv57xS21bho3C+oUZptQPM1jtVkmQ@mail.gmail.com>
To: Anne van Kesteren <annevk@annevk.nl>
Cc: DOM WG <www-dom@w3.org>
On Tue, Feb 12, 2013 at 7:07 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> I think we need to do two things here.
>
> 1. Move everything from MouseEvent into the UI Events specification.
> http://dev.w3.org/csswg/cssom-view/#extensions-to-the-mouseevent-interface
> as a distinct definition does not work.
>
> 2. Define offsetX and offsetY as algorithms whose input is the target
> node. In particular they are not initialized like the other
> attributes, they are computed on getting. This is observable if you
> create a synthetic MouseEvent and dispatch it. (CSSOM View does not
> get this detail.) Conversely, offsetX and offsetY should not appear in
> the initialization dictionary for this event.
>
> This matters in particular for the shadow tree case where we mutate
> the target, but do not want to mutate offsetX and offsetY as that
> would require further event-specific caching.
>
> The subject prefix [D4E] is suggested in the UI Events draft, but I
> think that is in error now.
>
> UI Events: https://dvcs.w3.org/hg/d4e/raw-file/tip/source_respec.htm


I like it.

:DG<
Received on Tuesday, 12 February 2013 17:19:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 12 February 2013 17:19:51 GMT