-
Notifications
You must be signed in to change notification settings - Fork 24
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
Move shorthand phrases to WebIDL #27
Comments
Is this still the plan? |
Yes. |
I think most work and discussion on this will happen over in whatwg/webidl#490. I've just left a big comment summarizing the work as I see it at whatwg/webidl#490 (comment). Let's leave this open for tracking, but centralize discussion over there. |
Hurray, @Ms2ger fixed this! However, now we need to decide what to do with this document as the clashes are not great and currently causing DOM PRs to fail (e.g., whatwg/dom#763). |
I don't know how anything works. Is https://api.csswg.org/bikeshed/ not using the same database local builds do? @tabatkins? |
You have to do |
No longer export various promise-related operations as IDL is now the source of truth. Closes #27.
No longer export various promise-related operations as IDL is now the source of truth. Closes #27.
(Spinning this off from #10.)
WebIDL is generally where this kind of normative spec-writing tool belongs. They'd need to get a bit more formal. We'd keep informative summaries here, probably after moving them to the WebIDL section.
The text was updated successfully, but these errors were encountered: