vr event type names vs. event attribute names

[andreasplesch]

https://w3c.github.io/webvr/#interface-window

sensibly defines attribute names for various vr related events.

In the explanation of the attribute names, the language seems to equate the attribute name with the event type name.

However, event type names generally do not include the "on" prefix:

https://www.w3.org/TR/html51/webappapis.html#event-handlers-on-elements-document-objects-and-window-objects

The "onvrdisplayconnect" attribute's value would typically be an event listener's callback for the event of type "vrdisplayconnect", not "onvrdisplayconnect". Consequently, you would expect to use addEventListener("vrdisplayconnect", cb).

I believe this naming scheme is well established, so I am puzzled why webvr would deviate ? Unless I miss something ?

Does the event type name indeed include the "on" prefix for webvr ?

It may be necessary to explicitly define event type names or/and a mapping from event handler attribute names to event type names.

[cvan]

You are correct in calling this out. The IDL should use EventTarget. And we did some proposed interface changes to make the WebVR APIs work in a worker. See issue #152 and @Tojiro's PR: #116

[andreasplesch]

Thanks, closing if I may. This issue is already well covered in #116 and its discussion. I see if I can follow the thrust of the discussion there.