Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New specs for review #77

Closed
69 tasks done
github-actions bot opened this issue Jun 15, 2020 · 12 comments
Closed
69 tasks done

New specs for review #77

github-actions bot opened this issue Jun 15, 2020 · 12 comments
Labels
enhancement New feature or request

Comments

@github-actions
Copy link
Contributor

github-actions bot commented Jun 15, 2020

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.

@github-actions github-actions bot added the enhancement New feature or request label Jun 15, 2020
@dontcallmedom
Copy link
Member

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

@dontcallmedom
Copy link
Member

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

@dontcallmedom
Copy link
Member

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

@dontcallmedom
Copy link
Member

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:

@dontcallmedom
Copy link
Member

dontcallmedom commented Jun 16, 2020

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

@tidoust
Copy link
Member

tidoust commented Jun 17, 2020

https://www.w3.org/TR/service-workers-1/

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.

dontcallmedom added a commit that referenced this issue Jun 17, 2020
@dontcallmedom
Copy link
Member

https://www.w3.org/TR/service-workers-1/

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

@dontcallmedom
Copy link
Member

#95 deals with MathML AAM

@dontcallmedom
Copy link
Member

re WebXR test API, I've filed w3c/webdriver#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

@dontcallmedom
Copy link
Member

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.

@dontcallmedom
Copy link
Member

#102 to deal with an oversight

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants