W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2013

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

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Thu, 10 Jan 2013 13:29:23 -0500
Message-ID: <50EF0883.30700@mit.edu>
To: Vincent Scheib <scheib@google.com>
CC: Anne van Kesteren <annevk@annevk.nl>, Tantek Çelik <tantek@cs.stanford.edu>, Webapps WG <public-webapps@w3.org>
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 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.


Received on Thursday, 10 January 2013 18:29:54 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:58 UTC