On Thu, 16 Jun 2016 12:33:30 +0200, Vincent Scheib <sch...@google.com>
wrote:
An accessibility review and handling of this [accessibility issue #1] are
still needed and will likely cause a CR cycle. To avoid unnecessary work
I propose CR to be deferred until that work is complete.
[accessibility issue #1] https://github.com/w3c/pointerlock/issues/1
Agreed, that makes good sense. I'll try to help that get done as fast as
we can.
cheers
On Tue, Jun 14, 2016 at 2:57 PM, Dylan Barrell <dylan.barr...@deque.com>
wrote:
abstain
On Tue, Jun 14, 2016 at 1:47 AM, Michiel Bijl <mich...@agosto.nl> wrote:
Looks good, +1
—Michiel
On 13 Jun 2016, at 18:12, Léonie Watson <t...@tink.uk> wrote:
Hello WP,
This is a Call For Consensus (CFC) to request that W3C republish
Pointer
Lock as a Candidate Recommendation (CR). Extensions to the
MouseEventInit
Dictionary [1] constitute substantive changes to the specification that
were
made after the current CR was published in 2013 [2].
Please reply to this CFC no later than 21st June 2016. Positive
responses
are preferred and supporting comments (beyond just +1) are encouraged,
but
silence will be considered as consent.
Thank you.
Léonie on behalf of the WP chairs and team, and Pointer Lock editor.
[1]
https://w3c.github.io/pointerlock/#extensions-to-the-mouseeventinit-dictiona
ry
[2] http://www.w3.org/TR/2013/CR-pointerlock-20131217/
--
@LeonieWatson tink.uk Carpe diem
--
Download the aXe browser extension for free:
Firefox: https://addons.mozilla.org/en-US/firefox/addon/axe-devtools
Chrome:
https://chrome.google.com/webstore/detail/axe/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US
Life is ten percent what happens to you and ninety percent how you
respond
to it. - Lou Holtz
--
Charles McCathie Nevile - web standards - CTO Office, Yandex
cha...@yandex-team.ru - - - Find more at http://yandex.com
