Re: [PointerLock] Should there be onpointerlockchange/onpointerlockerror properties defined in the spec from Anne van Kesteren on 2013-04-11 (public-webapps@w3.org from April to June 2013)

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 11 Apr 2013 18:23:03 +0100
To: Vincent Scheib <scheib@google.com>
Cc: Simon Pieters <simonp@opera.com>, Webapps WG <public-webapps@w3.org>, Boris Zbarsky <bzbarsky@mit.edu>
Message-ID: <CADnb78gX=jr2uoRyGYkDwWAODsfEOdbY9o4zKRWWcJD-XcdsYA@mail.gmail.com>

On Thu, Apr 11, 2013 at 5:59 PM, Vincent Scheib <scheib@google.com> wrote:
> 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.

So how much can we still change fullscreen? It should really use futures.


--
http://annevankesteren.nl/

Received on Thursday, 11 April 2013 17:23:30 UTC