Re: [PointerLock] Should there be onpointerlockchange/onpointerlockerror properties defined in the spec

What objects should these be exposed on? In previous discussions, if I
recall correctly, arguments were made for ~"the spec states the event is
dispatched to the document"~ but also e.g. webkit's implementation of
fullscreen bubbles from the target element, so perhaps you sould be able to
listen on everything. In the webkit pointer lock implementation events go
only to the document.

I suggest we expose the properties only on document, unless someone can
communicate the value of also including them on other elements.

I'm confused why HTML should include the properties, and not the respective
specifications.


On Thu, Jan 10, 2013 at 10:29 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> On 1/10/13 1:19 PM, Vincent Scheib wrote:
>
>> The pointer lock specification intentionally mimics the fullscreen
>> specification to provide consistency for developers, as they are similar
>> and expected to be commonly used in the same apps. Neither specification
>> mention event properties.
>>
>
> But HTML5 mentions onfullscreenchange/**onfullscreenerror.  Right now it
> only puts it on window/body/frameset, but not on document or any other
> node.  See https://www.w3.org/Bugs/**Public/show_bug.cgi?id=20637<https://www.w3.org/Bugs/Public/show_bug.cgi?id=20637>that I filed earlier today.
>
>
>  Mozilla and Chrome implement
>> document.on<prefix>**fullscreenchange
>> document.on<prefix>**fullscreenerror
>> document.on<prefix>**pointerlockchange
>> document.on<prefix>**pointerlockerror
>>
>
> Mozilla currently puts these properties on all HTML elements and on
> Document and Window, for what it's worth.
>
>
>  Pending agreement to add properties to the fullscreen specification, I
>> agree this should be included in the specification.
>>
>
> Please!
>
> -Boris
>
>