- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Jul 2024 23:29:35 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-cascade] Allow declarations directly in @scope?`, and agreed to the following: * `RESOLVED: allow bare declarations in a top level scope rule` <details><summary>The full IRC log of that discussion</summary> <khush> miriam: we just said that when scope is nested, we can put bare decls inside of it. scope is a bit different from other at-rules in that it changes the selector somewhat and has own selector built-in.<br> <khush> so we could allow bar declarations at any level it doesn't need to nested<br> <khush> so we could say this is also allowed when its not nested<br> <khush> matthieud: allowing declarations inside of scoped rule which are top level?<br> <khush> miriam: yup<br> <khush> i don't feel strongly about it but feels consistent if we allow in nested situations. so why not root?<br> <khush> andruud: agreed would be weird<br> <khush> also part of the reason to not do initially was we din't jhave relaxed nesting. so couldn't distinguish between selectors starting with tag names<br> <khush> astearns: +1<br> <khush> astearns: anyone needs time before resolving?<br> <khush> proposed resolution: allow bare declarations in a top level scope rule.<br> <khush> matthieud: in the cssom the declarations will be represented by a rule in a CSSNestedRule object?<br> <khush> andruud: yes<br> <khush> astearns: objections?<br> <khush> RESOLVED: allow bare declarations in a top level scope rule<br> <khush> miriam: if someone screams, we can revisit<br> <khush> matthieud: happy to discuss the other issue you mentioned<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10389#issuecomment-2207499764 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 July 2024 23:29:35 UTC