[uievents] Clarify or change the use of "default action" to avoid confusion (#22)

Copied from W3C Bugzilla: https://www.w3.org/Bugs/Public/show_bug.cgi?id=25844

##### Travis Leithead [MSFT] 2014-05-21 00:16:36 UTC
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.

##### Comment 1 Travis Leithead [MSFT] 2014-05-21 00:17:05 UTC
See also: https://www.w3.org/Bugs/Public/show_bug.cgi?id=12230#c25

##### Comment 2 Travis Leithead [MSFT] 2014-05-30 18:58:24 UTC
>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.

##### Comment 3 Arthur Barstow 2015-03-21 15:12:04 UTC
Bulk move of all D3E bugs to the UI Events component.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/22