Remove "DOM Event Architecture" from spec

[garykac]

The section in question: https://w3c.github.io/uievents/#dom-event-architecture

This section give a non-normative summary of event dispatch and event flow, but it also contains info that can cause confusion (eg: "default actions"). Much of this is normatively specified in DOM spec, and the useful bits need to be moved into the appropriate algorithm.

• 3.1. Event dispatch and DOM event flow
  • Delete this section. This is defined normatively in the DOM spec. No need to provide competing, non-normative definitions.
  • It is worthwhile to copy this into a separate document before deleting?
    • If so, update the links so that they point to the proper definitions.
• 3.2. Default actions and cancelable events
  • Delete this section. "Default actions" aren't really a defined thing and cancelability is complicated and needs to be defined as part of the algorithm for each event.
  • See Events do not have "default action"s #104 and Clarify or change the use of "default action" to avoid confusion #22
• 3.3. Synchronous and asynchronous events
  • Delete this section. Sync vs async needs to be part of the algorithm. This section just states that events can be either sync or async.
• 3.4. Trusted events
  • Move info about the click event and "default action" into the algorithm for MouseEvents.
  • Delete this section. isTrusted and friends are all defined properly in DOM. This spec should simply be using isTrusted in the algorithms.
• 3.5. Activation triggers and behavior
  • Delete this section. It basically says that "activation behaviors" can happen in response to "activation triggers", which is not terribly insightful or useful. As stated elsewhere: these behaviors need to be defined in an algorithm.
• 3.6. Constructing Mouse and Keyboard Events
  • Move relevant parts into KeyboardEvent section
  • Move relevant parts into MouseEvent section
  • Delete this section.

[Kaiido]

Regarding 3.3, it seems the concept of async/sync events isn't explained anywhere anymore though (unless I missed it). Given it's quite prominent in every event defs and tables, it's relatively confusing what these refer to.