UI Event spec modernization task list

[garykac]

This tracks the tasks that need to be completed in order to modernize the UI Events spec.

• [x] Discuss splitting spec into smaller parts (see https://github.com/w3c/uievents/issues/369)
  • [x] Decision not to split spec, but go ahead with modernizing sections
• [x] Remove "Changes" section (see https://github.com/w3c/uievents/issues/373)
• [ ] Convert MouseEvent to algorithms
  • [x] Add algorithm section to MouseEvent
  • [ ] Remove informal description once the algorithms are mature
• [ ] Convert KeyboardEvent to algorithms
  • [ ] Add algorithm section to KeyboardEvent
  • [ ] Remove informal description once the algorithms are mature
• [ ] Convert CompositionEvent to algorithms
  • [ ] Add algorithm section to CompositionEvent
  • [ ] Remove informal description once the algorithms are mature
• [ ] Convert WheelEvent to algorithms
  • [ ] Add algorithm section to WheelEvent
  • [ ] Remove informal description once the algorithms are mature
• [ ] Convert InputEvent to algorithms
  • [ ] Add algorithm section to InputEvent
  • [ ] Coordinate with Editing TF about links and cross-refs since many algorithms will be there.
  • [ ] Remove informal description once the algorithms are mature
• [ ] Move Focus Events info into HTML spec
  • [ ] Verify all info is present in HTML. Check cross-refs and links.
  • [ ] Delete section from UIEvents
• [x] Remove "DOM Event Architecture" section (see https://github.com/w3c/uievents/issues/372)
• [ ] Remove "Glossary" section
  • [ ] All definitions should be either (a) migrated to an appropriate section of the spec, or (b) deleted if they are already defined elsewhere

[mustaqahmed]

FYI @plehegar @patrickhlauke @flackr We discussed the need for algorithmic event dispatch text in Pointer Events few weeks ago, and concluded that we need to wait for the UI event algorithms to land first.