DOM events: differences between "interface" names and "feature" names

I believe the plural is odd but correct

http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-document

As an example, a user wishing to synthesize some kind of UIEvent would call createEvent with the parameter "UIEvents".

To create an instance of the MutationEvent interface, use the feature string "MutationEvents"

Note: To create an instance of the Event interface for the HTML event module, use the feature string "HTMLEvents" as the value of the input parameter used with the createEvent method of the DocumentEvent interface.

etc. By feature string, they mean the input into createEvent

Which browser support the singular version?

ahh thanks for the update. I looked for DOM3 Events, but didn't find it at first blush.

Let me re-read. It will be a snap to fix/update either way!

--nickg

Touch events make as much sense as mouse events. A headless browser has no less of a touch interface than it does of a mouse interface.

I'll end up doing this at some point ... unless someone else gets to it first :)

@diego -- given my task list, I probably won't get around to writing them, but you can! Patches very welcome for additional event types! Let me know if you need help getting started.

Hi. To help me understand your needs, what you use touchevent for. A
simple stub would be easy, but not sure if it is enough

I brought up touch events. At the base level, it's just a matter of creating the necessary event types and having the right fields.

How to use them is a more open issue, as are all the events that include screen coordinates. It's still an open issue in my mind that, at least for me, I'll get to as I start doing TDD for touch applications.

Lots of interesting little things ... there'a weird hierarchy of touch events vs mouse/click events vs. gesture events (zoom/rotate). Not really sure what the value/effort ratio is going to turn out on this. At the same time, manual testing is expensive.

So it'll be an interesting adventure.