-
Notifications
You must be signed in to change notification settings - Fork 715
[snapshot-2017] Candidate modules for inclusion #826
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
Comments
I made an edit to that list to fix one duplicate I caught. Looking through the list of things that aren't included, I think things worth considering to add to the "fairly stable but beware" level (although I'd probably lean against inclusion on some of them) are: We should also think about whether things like cssom, cssom-view, and the houdini specs should be part of a snapshot if they're stable enough. |
I see no reason not to, if they are stable enough. |
@dbaron I agree on your list of fairly stable but beware specs (maybe not ruby), but how about also including css-break? implementation is somewhat spotty, but the spec itself seems to me to be in good shape, and quoting the introduction:
|
Also, snapshot 2015 promises that indices of properties, functions etc are coming: Snapshot 2017 should link to the specific sections:
because the indices are not well known at present. |
We just discussed in the WG meeting, and concluded: Add to primary section: Add to rough interop section: Add to completed design section: |
Closed by f1adcde |
As requested by @dbaron on 2016-12-21 CSS call. All modules (CSS and fxtf) sorted by already-there, will-include, and the rest.
https://github.com/w3c/csswg-drafts/blob/master/snapshot-2017-modules.md
The text was updated successfully, but these errors were encountered: