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: Anne van Kesteren <annevk@annevk.nl>
Date: Sat, 16 Mar 2013 15:05:49 +0000
Message-ID: <CADnb78i8z0WEQhgkdKWV5V9yvxdFRvAHMz9pLNXGzJUTddRsMg@mail.gmail.com>
To: Vincent Scheib <scheib@google.com>
Cc: Simon Pieters <simonp@opera.com>, Webapps WG <public-webapps@w3.org>, Boris Zbarsky <bzbarsky@mit.edu>
On Fri, Mar 15, 2013 at 6:57 PM, Vincent Scheib <scheib@google.com> wrote:
> I have added onipointerlockchange and onpointerlockerror to the partial
> document IDL in the pointer lock specification.
> Webkit currently only defines these event handler attributes on document.
> Unless a reason is raised to add them elsewhere, I do not plan to add
> additional attributes elsewhere, for reasons discussed in fullscreen
> specification primarily regarding the confusing when releasing exiting due
> to an element being removed from the DOM, and confusion over multiple
> listener points.
> https://dvcs.w3.org/hg/pointerlock/raw-file/default/index.html
> https://dvcs.w3.org/hg/pointerlock/diff/86bc101925d8/index.html

FWIW, in https://www.w3.org/Bugs/Public/show_bug.cgi?id=20637 Ian
argues for Window/<body> due to their bubbling nature.

Received on Saturday, 16 March 2013 15:06:16 UTC

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