25844 2014-05-21 00:16:36 +0000 Clarify or change the use of "default action" to avoid confusion 2015-10-07 04:13:15 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - UI Events unspecified PC Windows NT RESOLVED MOVED P2 normal --- 1 travil garykac annevk garykac mike public-webapps www-dom public-webapps-bugzilla oldest_to_newest 106525 0 travil 2014-05-21 00:16:36 +0000 See: http://lists.w3.org/Archives/Public/public-webapps/2014AprJun/0519.html the "default action" can be interpreted as something belonging to the event dispatch mechanism, when in reality it is not. 106526 1 travil 2014-05-21 00:17:05 +0000 See also: https://www.w3.org/Bugs/Public/show_bug.cgi?id=12230#c25 107056 2 travil 2014-05-30 18:58:24 +0000 From Anne van Kesteren: 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. 118760 3 art.barstow 2015-03-21 15:12:04 +0000 Bulk move of all D3E bugs to the UI Events component. 123557 4 garykac 2015-10-07 04:13:15 +0000 Now tracking as: https://github.com/w3c/uievents/issues/22