Conversation
|
Good work, The format you propose for the table is good, needed for exiting CR, but not needed at all for entering it. For that we just need ot state the exit criteria and link to a report page that can be this CR Plan (but it can even be empty, at publication time, as it just needs to be complete when we exit). We basically just need to prepare the v1 CR doc and add in the SoTD that information (I can take care of that once the doc is ready) |
|
@jakearchibald @ylafon, let's publish a CR. I think we can use this PR document to track CR progress (test coverage and compat) after we publish the first CR version. @jakearchibald, please take a look at the following PRs. I'd like to merge them to publish a CR. #1151 (Approved, I’m checking if we need a separate test for SW.) From the V1 issue list, #732 will be closed by merging #1329. I'd like to move other issues to V2. They are dependent to works in HTML and DOM. |
|
As discussed on irc, we also need to select the test relevant to V1 only. |
|
@jungkees @jakearchibald I think this PR is probably obsolete now? |
This is a CR plan with a WIP table that maps WPT tests to each spec feature.
@ylafon @jakearchibald @jatindersmann - I'd like to discuss if this format and the information (that will be filled in the table) will meet the requirement to proceed and exit CR.
FYI, I asked @tabatkins if Bikeshed will support some feature to annotate the WPT status directly in the spec, and the answer was yes with no concrete schedule yet - at the end of the year at the earliest.
Until then, I plan to continue with this work. WDYT?