-
Notifications
You must be signed in to change notification settings - Fork 690
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
[css-scoping] Publish an updated WD #6370
Comments
@tabatkins any objection to putting out an updated WD? The last one dates to 2014. |
The changes section looks good, though a quick check for later changes is in order. |
I just re-checked the list of changes. We really should publish an updated WD, there are a lot of changes since 2014!!! Proposed Async resolution: Publish an updated Working Draft of CSS Scoping 1 @astearns @tabatkins @fantasai or we could use the generic "publish a working draft" resolution, in which case feel free to remove the Async label. |
The CSSWG will automatically accept this resolution one week from now if no objections are raised here. Anyone can add an emoji to this comment to express support. If you do not support this resolution, please add a new comment. Proposed Resolution: Publish an updated working draft of CSS Scoping 1 |
There was a previous discussion where we resolved to rename this spec, since it doesn't include scoping any more. |
Thanks @mirisuzanne has that integration work happened, or is it yet to be done? |
I see that it has not, CSS Shadow Parts is still a separate draft. |
Looks like we keep resolving to publish this and indeed we keep trying to rename it to CSS Shadow, too. |
There are many substantive changes to this document since the 2014 FPWD, and there is active interest in scoping.
Should we publish a new WD?
The text was updated successfully, but these errors were encountered: