On 21/06/2016 13:14, Léonie Watson wrote:
Important: This CFC is extended for 48 hours. Please provide comments by
end of day on Thursday 23^rd June 2016.
With thanks to those who responded, this CFC passes. We will begin the
process of transitioning Pointer Lock to CR.
Léonie.
--
@LeonieW
From: Léonie Watson [mailto:t...@tink.uk]
Sent: 21 June 2016 11:18
Yes, CR requires at least two implementations in shipping browsers. Once
Pointer Lock is at Recc, hopefully the Shadow DOM content will be stable enough
to include in Pointer Lock next.
Correction: A CR doesn’t require 2+ im
From: Takayoshi Kochi [mailto:ko...@google.com]
“I'm fine without Shadow DOM changes, because no one yet implemented the
intended change to the spec yet,
and so it could be immature to include in a "CR". (Does CR require at least 2
implementors exist?)”
Yes, CR requires at least two
Important: This CFC is extended for 48 hours. Please provide comments by end of
day on Thursday 23rd June 2016.
From: Vincent Scheib [mailto:sch...@google.com]
Sent: 21 June 2016 05:09
“I've discussed more with Xiaoqian and Léonie and support a CR now with this
proposal:
Move to a CR for
I'm fine without Shadow DOM changes, because no one yet implemented the
intended change to the spec yet,
and so it could be immature to include in a "CR". (Does CR require at
least 2 implementors exist?)
On Tue, Jun 21, 2016 at 1:09 PM, Vincent Scheib wrote:
> I've discussed more with Xiaoqian
I've discussed more with Xiaoqian and Léonie and support a CR now with this
proposal:
Move to a CR for the v1 Pointer Lock specification without Shadow DOM
changes, and a note on accessibility. Implementations are nearly consistent
for v1 and it can move to a published status sooner. We can follow
From: Vincent Scheib [mailto:sch...@google.com]
Sent: 16 June 2016 12:34
“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.”
I think
I'm working on updating text to incorporate Shadow DOM in pointer lock
spec.
https://github.com/w3c/webcomponents/issues/192
On Thu, Jun 16, 2016 at 2:06 PM, Vincent Scheib wrote:
> Shadow dom concepts will also be incorporated.
>
> On Thu, Jun 16, 2016 at 1:43 PM, Chaals McCathie Nevile <
> cha
Shadow dom concepts will also be incorporated.
On Thu, Jun 16, 2016 at 1:43 PM, Chaals McCathie Nevile <
cha...@yandex-team.ru> wrote:
> On Thu, 16 Jun 2016 12:33:30 +0200, Vincent Scheib
> wrote:
>
> An accessibility review and handling of this [accessibility issue #1] are
>> still needed and w
On Thu, 16 Jun 2016 12:33:30 +0200, Vincent Scheib
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] ht
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
On Tue, Jun 14, 2016 at
abstain
On Tue, Jun 14, 2016 at 1:47 AM, Michiel Bijl wrote:
> Looks good, +1
>
> —Michiel
>
> On 13 Jun 2016, at 18:12, Léonie Watson 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 M
Looks good, +1
—Michiel
> On 13 Jun 2016, at 18:12, Léonie Watson 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
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 rep
14 matches
Mail list logo
