Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove "DOM Event Architecture" from spec #372

Open
17 tasks
garykac opened this issue Feb 8, 2024 · 0 comments
Open
17 tasks

Remove "DOM Event Architecture" from spec #372

garykac opened this issue Feb 8, 2024 · 0 comments

Comments

@garykac
Copy link
Member

garykac commented Feb 8, 2024

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
  • 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant