W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2014

Re: Pointer Lock Status

From: Brandon Jones <bajones@google.com>
Date: Thu, 3 Apr 2014 14:02:11 -0700
Message-ID: <CAEGwwi34f2TdZLbP45uCsb4zCrFN_0mpB6hiRcTWJq8KYCPj7Q@mail.gmail.com>
To: Vincent Scheib <scheib@google.com>
Cc: Webapps WG <public-webapps@w3.org>
On http://status.modern.ie/ Microsoft lists Pointer Lock as still "Under
Consideration"


On Thu, Apr 3, 2014 at 1:38 PM, Vincent Scheib <scheib@google.com> wrote:

> Implementation status:
> Chrome: Implemented with prefix, in stable version.
> Firefox: Implemented with prefix, in stable version.
> IE: No implementation progress known. Issue:
> http://connect.microsoft.com/IE/feedback/details/793718/ie11-feature-request-support-for-pointer-lock-api
> Safari: No implementation progress known.
> Opera: No implementation progress known.
>
> Test suite status:
> Two basic tests exist:
> http://w3c-test.org/pointerlock/constructor.html
> http://w3c-test.org/pointerlock/idlharness.html
> which fail in Chrome and Firefox due to prefixing, and likely correctness
> issues are masked by this.
>
> Plan to "complete" test suite:
> - Implementations need to start using W3C tests that exist
>   - Thus implementations need to support unprefixed pointer lock.
>   - Chromium issue:
> https://code.google.com/p/chromium/issues/detail?id=359740
> - More tests are needed.
>   - Chromium and Mozilla have possible candidates for upstreaming.
>     - I sense little prioritization from either organization to do this
> soon. (Correct me if Mozilla has anyone available to do this)
>
> Additional specification discussion:
> Artillery started a discussion "Problems with mouse-edge scrolling and
> games" in public-webapps Feb 21 2014 raising the topic of limiting pointer
> movement to a rectangular area. This is addressed in the spec FAQ for why
> it is postponed from the initial version, and in the recent thread the
> result was a call for prototype. I don't have resources to build it out,
> though would accept others doing so. If this was done rapidly and Mozilla
> was interested in incorporating changes as well there's the possibility
> that Pointer Lock spec should be updated to include clipping. Otherwise, I
> believe a follow up specification at a later time is more appropriate,
> keeping Pointer Lock narrow and moving to complete the specification.
>
Received on Thursday, 3 April 2014 21:02:39 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:23 UTC