Re: CFC: Republish Pointer Lock as CR

2016-06-25 Thread Léonie Watson


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.

--
@LeonieWatson tink.uk Carpe diem



RE: CFC: Republish Pointer Lock as CR

2016-06-21 Thread Léonie Watson
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+ implementations, but we do have to 
demonstrate that the spec has received wide review. The implementations are 
needed to exit CR as we move to PR though. Sorry, my fault for not paying 
attention!

 

We plan to move Pointer Lock to CR, then to Recc within a few weeks. It seems 
like the most painless way to do things.

 

The alternative was to include the Shadow DOM features but mark them as “at 
risk” during the CR. Given that Shadow DOM is still not stable, it’s likely 
we’d have to take those features out again for PR – which seems like extra work 
for the editor.

 

Instead we encourage the editors to publish a WD of Pointer Lock 2 as soon as 
there is concensus on the Shadow DOM content.

 

 

 

HTH

Léonie.



RE: CFC: Republish Pointer Lock as CR

2016-06-21 Thread Léonie Watson
 

 

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 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.

 

 

Thanks for your help with this.

 

 

 

-- 

@LeonieWatson tink.uk Carpe diem

 

Léonie.



RE: CFC: Republish Pointer Lock as CR

2016-06-21 Thread Léonie Watson
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 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 up with a v2 requiring 
more implementation work afterwards.”

 

Thanks Vincent.

 

Per the note above, this CFC [1] is extended for 48 hours to give WG members 
more time to respond now we have clarified the path.

 

Léonie.

[1] https://lists.w3.org/Archives/Public/public-webapps/2016AprJun/0127.html 

 

 

 

-- 

@LeonieWatson tink.uk Carpe diem

 

 



Re: CFC: Republish Pointer Lock as CR

2016-06-21 Thread Takayoshi Kochi
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 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 up with
> a v2 requiring more implementation work afterwards.
>
>


-- 
Takayoshi Kochi


Re: CFC: Republish Pointer Lock as CR

2016-06-20 Thread Vincent Scheib
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 up with
a v2 requiring more implementation work afterwards.


RE: CFC: Republish Pointer Lock as CR

2016-06-17 Thread Léonie Watson
 

 

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 the issue can be resolved with an informative note in the spec. It’s a 
question of what the browser does in accessibility terms once a 
pointerlockchange event has been fired.

 

Will post this to the GH issue in a moment… but don’t believe this should hold 
up the CFC.

 

Léonie.

 

 

 

 

[accessibility issue #1] https://github.com/w3c/pointerlock/issues/1

 

On Tue, Jun 14, 2016 at 2:57 PM, Dylan Barrell  > wrote:

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 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

 

 



Re: CFC: Republish Pointer Lock as CR

2016-06-16 Thread Takayoshi Kochi
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...@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 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 
>>> wrote:
>>>
>>> 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
> 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
>>
>>
>


-- 
Takayoshi Kochi


Re: CFC: Republish Pointer Lock as CR

2016-06-16 Thread Vincent Scheib
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 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 
>> wrote:
>>
>> 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
 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
>
>


Re: CFC: Republish Pointer Lock as CR

2016-06-16 Thread Chaals McCathie Nevile
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] 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 
wrote:


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  
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



Re: CFC: Republish Pointer Lock as CR

2016-06-16 Thread Vincent Scheib
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 2:57 PM, Dylan Barrell 
wrote:

> 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 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
>
>


Re: CFC: Republish Pointer Lock as CR

2016-06-14 Thread Dylan Barrell
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 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


Re: CFC: Republish Pointer Lock as CR

2016-06-14 Thread Michiel Bijl
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 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
> 
> 
>