Should we add a firesPointerEvents property?

[jacobrossi]

Since there are some UI Events that fire pointer events and some that don't, do we want a firesPointerEvents property for completeness?

[jacobrossi]

Likewise, firesMouseEvents might be useful for scenarios such as knowing if an Enter keypress is going to produce a click event.

[RByers]

Are you suggesting that you'd get a different InputDevice object depending on context (event target, etc.)? Or do the properties on a given device change with context (i.e. the keyboard device has a firesMouseEvents that becomes true briefly after hitting space on a checkbox). Modeling after the APIs in other OSes, I expected we'd want something context-free (eg. Imagine an API to enumerate all devices like we've discussed before in PEWG). Maybe you're talking about new properties of a UIEvent, rather than other properties of InputDevice?

Still, I wondered if (static) properties like those might be valuable InputDevice (certainly "is this a pointer" from the point of view of PE). I don't have particularly compelling scenarios off the top of my head though, so I was trying hard to keep the first rev very focused. See the brainstorm doc in the readme for more API ideas from various folks.