- From: Olli Pettay <Olli.Pettay@helsinki.fi>
- Date: Wed, 03 Oct 2012 00:52:37 +0300
- To: Florian Bösch <pyalot@gmail.com>
- CC: Chris Pearce <cpearce@mozilla.com>, Vincent Scheib <scheib@google.com>, Arthur Barstow <art.barstow@nokia.com>, "public-webapps@w3c.org" <public-webapps@w3c.org>
On 10/02/2012 11:55 PM, Florian Bösch wrote: > I'd like to point out that vendors are using additional failure criteria to determine if pointerlock succeeds that are not outlined in the > specification. Firefox uses the fullscreen change event to determine failure and chrome requires the pointer lock request to fail if not resulting > from a user interaction target. I think that Firefoxes interpretation is less useful than Chromes, But safer and that Chromes interpretation should be amended > to the spec since it seems like a fairly good idea. > I'm not yet convinced that it is safe enough. Also, it is not properly defined anywhere. > On Tue, Oct 2, 2012 at 10:37 PM, Chris Pearce <cpearce@mozilla.com <mailto:cpearce@mozilla.com>> wrote: > > On 27/09/12 08:37, Vincent Scheib wrote: > > On Wed, Sep 26, 2012 at 9:17 AM, Arthur Barstow <art.barstow@nokia.com <mailto:art.barstow@nokia.com>> wrote: > > On 9/26/12 11:46 AM, ext Vincent Scheib wrote: > > On Wed, Sep 26, 2012 at 7:27 AM, Arthur Barstow <art.barstow@nokia.com <mailto:art.barstow@nokia.com>> > wrote: > > * Pointer Lock - Vincent - what's the status of the spec and its > implementation? > > Firefox 14 and Chrome 22 shipped Pointer Lock implementations to > stable channel users recently. (Check out this Mozilla demo > https://developer.mozilla.org/__en-US/demos/detail/bananabread <https://developer.mozilla.org/en-US/demos/detail/bananabread>__, using > either.) > > Pointer Lock specification did have minor adjustments (inter-document > and iframe sandbox security issues, pending state and mouse movement > clarifications). diffs: > http://dvcs.w3.org/hg/__pointerlock/log/default/index.__html <http://dvcs.w3.org/hg/pointerlock/log/default/index.html> > > So, I'm happy to prepare an updated working draft. > > > Thanks for the update Vincent! > > Do you and/or the implementers consider the spec feature complete, which is > a major factor to determine if the spec is "Last Call ready" (other > considerations are documented at [1])? > > There are no known issues, and no known additional features. We > haven't seen many applications developed yet, but there have been a > few functionally complete demos. Reading over [1] I believe it is > "Last Call Ready". > > > I agree. No one involved on our side of things is aware of any remaining issues with the pointer lock spec. > > > Chris Pearce > (Mozilla's pointer lock implementation maintainer) > > > >
Received on Tuesday, 2 October 2012 21:53:18 UTC