Re: CFC Selectors API L1 to CR/PR

On Mon, 15 Oct 2012 23:13:53 +0200,  wrote:

> Formally, this is a Call for Consensus to move Selectors API to CR (and
> possibly direct to Proposed Recommendation - see below). Responses are  
> due by Friday 26 October, and while silence will be considered assent,
> formal approval is preferred. Please reply to this thread to indicate
> your response.

Yandex formally supports Selectors going forward.

cheers

Chaals

> In addition, we would appreciate any information implementors may be able
> to provide about proposed plans for fixing outstanding bugs in their
> implementations.
>
> The Selectors API Level 1 spec [1] has been fundamentally stable for  
> quite
> a while, and one issue was raised during Last Call, about what to do with
> comments. Since we are working on a level 2, Lachlan has proposed to  
> leave
> the comments case undefined for now and figure out what to do during the
> time Level 2 is finished, which has been accepted by the commenter [2].
>
> The existing test suite [3] has not been approved yet (a separate mail is
> coming on that) and Lachlan suggests it could use improvement, but it
> shows two independent browsers passing each test (Opera 12.1 snapshot and
> Firefox 16 Release both already pass the ns|div tests that are listed as
> having no passes in the implementation report linked. General-purpose
> sites like caniuse.com claim it is "implemented everywhere". If it is
> possible to satisfactorily demonstrate interoperable implementability, I
> propose to request a direct advance to proposed Recommendation.
>
> [1] http://www.w3.org/TR/selectors-api/
> [2] http://www.w3.org/mid/501FA594.8000903@oupeng.com
> [3]
> http://w3c-test.org/webapps/SelectorsAPI/tests/submissions/Opera/level1-baseline.html
>
>


-- 
Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
       chaals@yandex-team.ru         Find more at http://yandex.com

Received on Friday, 26 October 2012 15:55:59 UTC