-
Notifications
You must be signed in to change notification settings - Fork 79
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
Update Web IDL URLs to point to WebIDL Level 1. #107
Comments
Oops all of those appear to be covered by http://www.w3.org/TR/WebIDL-1/. Thus, we should update all URLs to use that version of the spec. I'll change the subject. The question about where to add |
In addition, conform that that all features we use are in Level 1. In addition to the https://heycam.github.io/webidl/ URLs, this should include checking all references for "WebIDL" (Look for exactly that string in the text.) |
For Level 1: Promises: My suggestion is to keep the references to https://heycam.github.io/webidl/ for now and do a separate overall analysis of the dependencies. Once we believe we're getting closed to stable for EME, that's when we should really worry about it. I'm willing to provide the analysis. I could do one for WebIDL now if you'd like me to but let's keep it separate from modified the draft for now. |
Per the telecon today, we should point to the latest and greatest and only worry about this in PR. I'm fine with closing this issue knowing that process will make us address this before PR. |
I was able to confirm with one of the WebIDL Level 1 editors that EME does not make use of any non-Level 1 definition or feature. |
imho, this issue can be closed. |
Thank you! |
The spec has a reference to WebIDL-1, but it also uses features of Web IDL (Second Edition) and contains links to https://heycam.github.io/webidl/.
Known items include:
iterable
(pending issue MediaKeyStatusMap: iterable declaration has unexpected behavior; ForEachCallback definition is incorrect #75)DOMException
use https://heycam.github.io/webidl/@plehegar for process issues. Also, @plehegar what's the best way to include a reference for something that is used throughout the spec or in the IDL?
The text was updated successfully, but these errors were encountered: