W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2013

Re: [pointerlock] Seeking status and plans

From: Vincent Scheib <scheib@google.com>
Date: Thu, 3 Oct 2013 09:14:37 -0700
Message-ID: <CAK-EfXkMMfCEaB4nzuiYuOeqyy_1uHuKqUr84Z__7Dnc=g8snw@mail.gmail.com>
To: Arthur Barstow <art.barstow@nokia.com>
Cc: public-webapps <public-webapps@w3.org>
On Wed, Oct 2, 2013 at 9:30 AM, Arthur Barstow <art.barstow@nokia.com>wrote:

> Hi Vincent,
>
> If any of the data for the Pointer Lock spec in [PubStatus] is not
> accurate, please provide corrections.
>

Pointer Lock is no longer blocked on mozilla security review. Firefox
stable now implements behavior similar to Chrome when not in full screen. I
will be updating the spec and closing
https://www.w3.org/Bugs/Public/show_bug.cgi?id=19297 soon.


> Also, if you have any new information re your plans for the spec - last
> published 29-May-2012 - or the spec's status with respect to being feature
> complete, implementation status, etc. please let us know.
>

I will update the specification to include the constraints now implemented
in Firefox and Chrome, but will leave wording allowing user agents to have
additional constraints as appropriate for future contexts.

I will also clarify the spec by adding reference to onpointerlockchange and
onpointerlock error, and specifying that pointer lock should not be exited
upon a transition in window state between fullscreen, maximized or restored.

At that point I would like to publish another working draft of the
specification, possibly a Last Call Working Draft.



>
> -Thanks, ArtB
>
> [PubStatus] <http://www.w3.org/2008/**webapps/wiki/PubStatus<http://www.w3.org/2008/webapps/wiki/PubStatus>
> >
>
Received on Thursday, 3 October 2013 16:15:38 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 3 October 2013 16:15:39 UTC