- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Fri, 30 May 2014 19:39:55 +0200
- To: Travis Leithead <travis.leithead@microsoft.com>
- Cc: Gary Kacmarcik (Кошмарчик) <garykac@chromium.org>, Domenic Denicola <domenic@domenicdenicola.com>, Philippe Le Hegaret <plh@w3.org>, "www-dom@w3.org" <www-dom@w3.org>
On Fri, May 30, 2014 at 7:09 PM, Travis Leithead <travis.leithead@microsoft.com> wrote: > The event dispatch flow, handling of canceled flag, etc., is already spec'd in DOM, Well, yes. However, D3E talks a lot about "default action". Instead, it should talk about a particular action occurring (such as the user pressing a key) as part of a system-level task and that action should then cause a number of steps to happen: 1. Gather enough data to create the appropriate event object. 2. Dispatch the created event at a node that is also determined somehow. 3. Check the event's canceled flag to see whether any "default action" can happen at this point. Note that I left a ton of stuff vague here. We should try to be less vague in the specification. > and we're actively dropping the normative requirements for that stuff as part of Bug 25485 Excellent. > I've now filed Bug 25927 [Specify the Event Loop integration for various non-deprecated events, incl. hit testing]. Thanks. -- http://annevankesteren.nl/
Received on Friday, 30 May 2014 17:40:23 UTC