Quick reminder that this CFC closes tomorrow, Saturday 20th August. Thanks.


@LeonieWatson tink.uk Carpe diem

On 14/08/2016 00:01, Xiaoqian Wu wrote:
Hello, Web Platform WG,

This is a Call for Consensus to publish a Proposed Recommendation of
Pointer Lock using the [PR] as the basis. Agreement with this CfC means
you consider the test results shows interoperability and the changes
since CR are not substantive.

The test results for Pointer Lock [All] indicate significant
interoperability, with only one test that have less than two passes [<2].
<http://www.w3c-test.org/pointerlock/idlharness.html>; this test failure
can be considered more of a Web IDL implementation issue. The group
believes it will get better over time as WebIDL compliance progresses.

The current [OPEN ISSUES], #5 is about adding pointerlock to the
permissions enum, will be fixed the next version. Another issue is
about pointerlockchange and the accessibility tree (#1), which is
resolved by a magnification software note added to pointerlockchange and
pointerlockerror Events.

Changes since the CR publication includes:
* Specify movementX/Y to be 0 after gaps in mouse input.

We consider the change since the CR as non-substantive. See [Diff] for
all of changes between the CR and the draft PR.

If you have any comments or concerns about this CfC, please reply to
this e-mail by August 20 at the latest. Positive response is preferred
and encouraged, and silence will be considered as agreement with the
proposal. If there are no non-resolvable objections to this proposal,
the motion will carry and we will request the PR be published on August
25 2016.



[PR] http://w3c.github.io/pointerlock/publish/index-2016-PR.html
[All] http://w3c.github.io/test-results/pointerlock/all.html
[<2] http://w3c.github.io/test-results/pointerlock/less-than-2.html
[OPEN ISSUES] https://github.com/w3c/pointerlock/issues

Reply via email to