Getting ready for CR

Hello group,


The next milestone for the HTML repository is called "HTML 5.2 CR 
draft". This is because it will be the one we propose as a Candidate 
Recommendation for HTML 5.2 - things that are not ready for it will go 
into the next version (presumably HTML 5.3…)


Candidate Recommendations are stable, and we need to show that we have 
implementation. The approach we have taken has been to demonstrate the 
new things in the specification are implemented - which is why we 
generally don't put requirements in the spec unless we can show they are 
met interoperably in implementation.


But we also mark things "at risk" - meaning we're not certain they will 
be implemented. The reason is that this way it is easier to remove them 
from the 5.2 version as it moves toward Recommendation.


So what does this mean?


First, if you're looking to contribute something, tests are always welcome…

Second, if there is something in the spec that you don't think works in 
practice, please add it to the list of things to consider "at risk" in 
issue 893: https://github.com/w3c/html/issues/893

Third, if there is something that you really wanted fixed in HTML 5.2, 
time is running short.

cheers

Chaals

-- 
Charles McCathie Nevile   -   standards   -   Yandex
chaals@yandex-team.ru - Find more at http://yandex.com

Received on Wednesday, 10 May 2017 12:40:00 UTC