- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Mar 2023 16:10:29 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-cascade-6] What is the desired shape of CSSScopeRule?`, and agreed to the following: * `RESOLVED: Accept the CSSScopeRule design, with the three changes noted in the thread.` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> miriam: Anders pushed a definition for the CSSSCopeRule, in the ED<br> <TabAtkins> miriam: We didn't ahve a resolution on the details tho, so wanted to clarify it's defined properly<br> <TabAtkins> miriam: Main qs in the thread are terms used for the start and end fo the scope (sometimes called "root" and "lower boudnary"/"scoping limit")<br> <TabAtkins> miriam: In thread we decided start/end were clearest terms, especially if we do sibling scopes - they keep making sense, while upper/lower dont'<br> <TabAtkins> miriam: Another q is what to return if one of the values isn't specified, we suggest null<br> <TabAtkins> miriam: Final q, should the value contain the parens around the selectors? Propose no.<br> <Rossen_> q?<br> <TabAtkins> miriam: So proposal is accept the CSSScopeRule, with the three conclusions outlined above.<br> <fantasai> +1<br> <bramus> +1<br> <TabAtkins> Rossen_: Looks like agreement in the thread, anyone have objections?<br> <TabAtkins> RESOLVED: Accept the CSSScopeRule design, with the three changes noted in the thread.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8626#issuecomment-1488904423 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 29 March 2023 16:10:31 UTC