[w3c/uievents] Need procedural algorithms for all events (#200)

This is a tracking bug for updating the UIEvents specification to make sure that all of the events have an appropriate procedural algorithm. The intent is that we should create specific issues for each topic, and keep discussions in these more directed issues.

Keyboard events: https://github.com/w3c/uievents/issues/142
Focus events: https://github.com/w3c/uievents/issues/195
Mouse (move) events: https://github.com/w3c/uievents/issues/196
Mouse (click) events: https://github.com/w3c/uievents/issues/197
Input events: https://github.com/w3c/uievents/issues/198
Composition events: https://github.com/w3c/uievents/issues/199

There will be some overlap as these algorithms interact with each other, but this seems like a reasonable starting point. Please feel free to add more issues as needed.

General design note:
Ideally, these algorithms should make it possible to add appropriate hooks so that other specifications can make localized changes to these algorithms.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/uievents/issues/200