Re: [w3c/uievents] Define events directly caused by user interaction (#270)

Would it be acceptable to have the following:

* Mouse, Keyboard, Wheel, Input and Composition events listed in a "User Interaction Events" section in UIEvents
* That section in UIEVents has a link to list in PointerEvents that defines "additional user interaction events"
* Similarly for Touch and DragAndDrop events (and any other specs that come in the future)

Advantage: If a new Pointer (or Touch, ...) event is added, it is more likely to be added to their list. Editors for those specs are less likely to think about updating UIEvents.

Disadvantage: Instead of a single list, there are multiple places to look to get the complete list.

-- 
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/270#issuecomment-671628328