- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Oct 2021 22:27:58 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `What is the appropriate syntax for appending to nested layers?`, and agreed to the following: * `RESOLVED: Leave the spec unchanged with dot syntax` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: What is the appropriate syntax for appending to nested layers?<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/5791<br> <dael> miriam: Allow to nest and then concat names and allow you to access. If you put theme inside framework you gat frameworktheme layer. What is syntax?<br> <dael> miriam: In spec we have dot between two. Other options are space or other divider.<br> <TabAtkins> @layer framework { @layer theme {...}} -> appendable via @layer framework.theme {...} in current spec<br> <dael> miriam: We have this behind a flag in browsers. Change before we release or is it okay?<br> <dael> astearns: Anyone with concerns about dot syntax?<br> <dael> astearns: Silence.<br> <dael> astearns: Prop: Leave the spec unchanged<br> <dael> astearns: Obj?<br> <dael> RESOLVED: Leave the spec unchanged with dot syntax<br> <fantasai> I used to be more in favor of spaces (but not strongly) but thinking about how we might need to extend the syntax, I think the dot syntax is better.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5791#issuecomment-937265907 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 October 2021 22:27:59 UTC