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

On Sat, Mar 16, 2013 at 8:05 AM, Anne van Kesteren <annevk@annevk.nl> wrote:

> 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.
>
> I argue on that issue that we should not bubble the event and have the
handler on document only. Pointer lock doesn't have as much legacy spec
churn as fullscreen, but I think we're in a position to have both of them
be cleaned up before un-prefixing.

Received on Thursday, 11 April 2013 17:00:06 UTC