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: Vincent Scheib <scheib@google.com>
Date: Thu, 10 Jan 2013 10:19:59 -0800
Message-ID: <CAK-EfXnE5+L4fLKZZzdkRsRnjw3Vk5KO7mLY+FEz63EJhPN8bw@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>, Anne van Kesteren <annevk@annevk.nl>, Tantek Çelik <tantek@cs.stanford.edu>
Cc: Webapps WG <public-webapps@w3.org>
[Including Anne & Tantek due to their work on Fullscreen]

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.

Mozilla and Chrome implement
document.on<prefix>fullscreenchange
document.on<prefix>fullscreenerror
document.on<prefix>pointerlockchange
document.on<prefix>pointerlockerror

Pending agreement to add properties to the fullscreen specification, I
agree this should be included in the specification.

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

> And if so, which objects should they be on?  Window?  Documents?  Elements?
>
> -Boris
>
>
Received on Thursday, 10 January 2013 18:20:56 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:57 GMT