Closed github-actions[bot] closed 4 years ago
checked off
https://www.w3.org/TR/input-events-1/ from w3c/input-events
https://www.w3.org/TR/resource-timing-1/ from w3c/resource-timing
since they're older versions of specs we're already tracking - #78 will make sure they no longer get reported
https://w3c.github.io/webappsec-cowl/ from w3c/webappsec-cowl https://w3c.github.io/webappsec-uisecurity/ from w3c/webappsec-uisecurity https://www.w3.org/TR/COWL/ from w3c/webappsec-cowl https://www.w3.org/TR/UISecurity/ from w3c/webappsec-uisecurity checked off given we'll ignore them via #79
Crossing this list with the list of specs mentioned in the Chrome status board, the following specs may be more likely candidates for consideration:
I've also filed #80 to expose links to Chrome status in the report on newly found specs.
I filed a pull request to add 3 of the IWWG specs #81 - I'm not sure how to deal with https://immersive-web.github.io/webxr-test-api/ - do we include WebDriver-only APIs in? shouldn't these APIs be exposed in a different global (e.g. to help with automated testing?)
I've filed #82 #83 #84 #85 #86 #87 #88 who deals with most of the identified specs.
Below the lists I haven't quite figured out yet:
with #89 #90 #91, the remaining list is
@tidoust can you make a proposal at least for the last category? your input on the other ones would be naturally welcome as well :)
Right, we just need to enable setting the ED URL in specs.json since the /TR/ spec currently links to a different ED.
https://gpuweb.github.io/WSL/ (we probably want it in, but it's not in a supported format?)
We probably do not want it in. This is the first and now historical proposal, the actual shadling language spec that the CG is working on is at: https://gpuweb.github.io/gpuweb/wgsl.html
unclear ownership across Media/WICG
These can be ignored, they have been or are being merged back into main MSE/EME repos.
Right, we just need to enable setting the ED URL in specs.json since the /TR/ spec currently links to a different ED.
Can you file an issue for that?
https://gpuweb.github.io/WSL/ (we probably want it in, but it's not in a supported format?)
We probably do not want it in. This is the first and now historical proposal, the actual shadling language spec that the CG is working on is at: https://gpuweb.github.io/gpuweb/wgsl.html
OK - should WGSL be added to the list then?
unclear ownership across Media/WICG
These can be ignored, they have been or are being merged back into main MSE/EME repos.
Can you get the WICG repos closed/redirected as needed then? :)
I've posted #93 to ignore these additional specs
re WebXR test API, I've filed https://github.com/w3c/webdriver/issues/1534 to see if we could find a way to distinguish WebDriver-targeted APIs.
In the meantime, I've filed #97 to push that spec in the monitor list
Added #98 and #99 to cover the last few specs; unless I missed something, I think once #94 is solved and the remaining PRs are merged, this issue should be closable.
find-specs has identified the following candidates as potential new specs to consider:
Please review if they match the inclusion criteria. Those that don't and never will should be added to ignore.json, those that don't match yet but may in the future can be added to monitor-repos.json, and those that do match should be brought as a pull request on specs.json.