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

UI Events

From: Anne van Kesteren <annevk@annevk.nl>
Date: Tue, 4 Feb 2014 13:30:44 +0000
Message-ID: <CADnb78gUdRGnx9dVy3QT6Ks5wCFR3RvsdsFCkTeBQHLafoFYaA@mail.gmail.com>
To: "www-dom@w3.org" <www-dom@w3.org>
I wonder what the current plan is with respect to UI Events. Is it
going to replace DOM Level 3 Events or is it merely going to add some

I would like UI events to be much better defined than they are
currently. I provided an illustration below of how far away we are
from that currently.

I think the current integration with the event loop mechanism is
poorly done. What I'd like to see is have events defined in response
to tasks queued by the underlying platform. E.g. when the platform
queues a task for mouse occurrence of sorts you'd run a set of steps:

1. Perform hit testing (ref CSS) to determine the layout box at the
given platform /x,y/ for viewport /v/.
2. Get the layout box's associated element.
3. Set element's hover flag.
4. Fire an event /e/ called /m/ with its various attributes set as follows ...
5. If /e/'s cancelled flag is unset, run ...

Obviously there's a bunch more here and some of the above depends on
the type of mouse input given and what mouse input has been given
until that point. And some of it such as hit testing are obvious black
boxes but it is better to acknowledge that than not mention it at all.

If we are serious about defining how this works this is the direction
we need to go in.

Received on Tuesday, 4 February 2014 13:31:11 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:22 UTC