Semantics behind list

[annevk]

https://wicg.github.io/event-timing/#considered-for-event-timing has a list of event types. How were these chosen?

[tdresser]

Our objective was to construct a list of the events which would be caused by directly by user input.
We should be clearer about this in the spec (and it's very possible we missed something!).

[annevk]

What about pointerrawupdate or any other new input event type? Would that require changes? If so, we should really abstract this somehow. The inert attribute @alice is working on would also benefit from this.

[tdresser]

Yeah, we should figure out how to abstract this somehow. I'm really not sure what the best approach to doing this is though. Would we just want to move the list to the DOMEvent spec?

[annevk]

Letting UI Events own it sounds like a good start, as "user interaction event types" or some such.

An alternative I somewhat prefer would be to set a specific internal slot on the Event object, "due to user interaction" or some such, at the time of firing. Specifications could then check for the value of this internal slot. New user interaction event specifications would have to set this bit appropriately in order to integrate with the ecosystem. This might be a bit more involved though as it'd require finding and updating all the relevant specifications, some of which don't have the appropriate infrastructure.

[tdresser]

The internal slot approach does seem preferable, that's a good thought.

[clelland]

@mmocny, can you take a look at the spec changes that would be required for this?