-
Notifications
You must be signed in to change notification settings - Fork 645
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 updated css-scoping-1 draft? #7494
Labels
Administrative Tracker
For external review / publication tracking issues.
css-scoping-1
Current Work
Comments
Looks like the changes section needs a minor update, it does not mention: but the previous few changes are all listed. |
svgeesus
added a commit
that referenced
this issue
Jul 20, 2022
svgeesus
added a commit
that referenced
this issue
Jul 20, 2022
…onsiderations, as now required for horizontal review. See #7494
Done. |
The CSS Working Group just discussed
The full IRC log of that discussion<emilio> topic: [css-scoping] Publish updated css-scoping-1 draft?<emilio> github: https://github.com//issues/7494 <emilio> lea_: I recently pulled up the spec and since drafts.csswg.org was down I used the last published draft <emilio> ... last published version is from 2014, which is too long ago <miriam> q+ <chris> +1 <emilio> chris: I just updated the draft changes so I think it should be good to publish <miriam> https://github.com//issues/5809#issuecomment-910896765 <Rossen_> ack miriam <emilio> Rossen_: given fantasai_ and TabAtkins are out happy to resolve and let them bring it back next week if needed <emilio> miriam: we resolved a while ago to reorganize some of the scoping features <emilio> [see comment above] <emilio> chris: I don't recall everything but some of those changes have been made <emilio> miriam: only concern is to keep clear what belongs where, but not opposed to republish <emilio> jensimmons: I think the scoping spec is not about scoping because those bits are from the cascade spec <emilio> ... there's confusion because there's a whole bunch of scoping ideas <chris> q+ <emilio> ... so if you search for css scoping you end up in the wrong place <emilio> ... so it'd be clearer if the spec was called shadow <emilio> ack chris <Rossen_> ack chris <emilio> chris: I'm in favor of pushing specs forward, but if we're going to cause confusion I'd rather wait a week or two <lea_> not sure anyone is actively following when a new draft is published… <chris> not opposed to a resolution <emilio> Rossen_: feedback is great to draw attention on some of the historical context. doubt tab / fantasai would press the button just because they see a resolution <emilio> ... we should capture everything needed to republish <chris> also good if the introduction had, well, text <chris> 1. Introduction ... <emilio> ... objections to republish when tab / fantasai are ready? <Rossen_> q? <emilio> RESOLVED: Republish when ready <jensimmons> And thanks lea_ for pointing out this needed to be republished! |
Maybe rename to CSS Shadow? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Administrative Tracker
For external review / publication tracking issues.
css-scoping-1
Current Work
Current published WD dates back to 2014! https://www.w3.org/TR/css-scoping/
There are several changes since then.
The text was updated successfully, but these errors were encountered: