W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2021

Re: [csswg-drafts] [css-cascade] What is the appropriate syntax for appending to nested layers? (#5791)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 27 Jan 2021 18:01:49 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-768467740-1611770508-sysbot+gh@w3.org>
The CSS Working Group just discussed `[css-cascade] What is the appropriate syntax for appending to nested layers?`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-cascade] What is the appropriate syntax for appending to nested layers?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/5791<br>
&lt;dael> miriam: In the layers spec we allow nesting of layers. Accessing nested layers through some syntax to say I'm not jsut adjusting default but defualt inside framework. What is syntax to combine<br>
&lt;dael> miriam: In spec we use a dot. framework.default framework.theme. Felt to some of us space is fine and more css-y<br>
&lt;dael> miriam: At the bottom I provided samples of proposals. / syntax. , syntax but we have that elsewhere for ordering.<br>
&lt;TabAtkins> q+<br>
&lt;fantasai> +1 to space<br>
&lt;dael> miriam: I think space is simpliest and communicates fine<br>
&lt;astearns> +1 to space, too<br>
&lt;leaverou> yeah avoid commas<br>
&lt;leaverou> ^ that was ChrisL<br>
&lt;dael> TabAtkins: I would be fine with space. But every time I look at this the dot looks really good. Probably my JS mind, but want to lean on it. Implies the nesting in a way the space doesn't<br>
&lt;dael> TabAtkins: Okay with space, but I really like the period<br>
&lt;dael> florian: One reason I'm not too hot on period is b/c this is new syntax I start to wonder if you can have spaces around period or css comments betwee. I suspect answer is yes and then it starts to drift from feels like JS<br>
&lt;dael> TabAtkins: I would say no spaces. Can't stop comments, but no space<br>
&lt;dael> fantasai: I agree with florian. B/c we don't have existing syntax this gets complicated. In terms of convaying nesting we doo it with a space in selectors<br>
&lt;TabAtkins> q+<br>
&lt;leaverou> q?<br>
&lt;dael> leaverou: Agree a space is more natural to css<br>
&lt;JonathanNeal> Strong agreement with the comment about periods. In CSS, a space can mean I’m configuring something, adding another value, and rarely does it mean I’m reaching into something.<br>
&lt;astearns> ack TabAtkins<br>
&lt;dael> TabAtkins: Analogy with selectors is why I'm uncomfortable with space. The direct nesting is the arrow and I don't want to do that.<br>
&lt;JonathanNeal> Oh, right, except for selector syntaxes, and I would not want to mentally parse the space as a kind of combinator.<br>
&lt;dael> TabAtkins: We don't want to imply other selecto syntax works. It's a bit foreign to css but similar to many other programming languages. Method chaining works exactly how we want. Dealing with space as combinator is only kinda sorta appropraite<br>
&lt;fantasai> yeah -1 to using ><br>
&lt;dael> astearns: Looks like TabAtkins and JonathanNeal like period. Everyone else has said space. Anyone else with period preference?<br>
&lt;dael> astearns: TabAtkins you said you would be okay using space? You wouldn't object?<br>
&lt;dael> TabAtkins: I won't object but I may want to revisit. Selectors is only place we use space to do nesting and that's not the right type of nesting to evoke. Not happy, but won't object<br>
&lt;JonathanNeal> In CSS, I prefer when space is just the absence of meaning.<br>
&lt;dael> fremy: one question. if we want to do search isn't using space a bit harder. Less searchable. If you use space you split the things apart. If you want ot use in properties it's more difficult<br>
&lt;TabAtkins> quick straw poll?<br>
&lt;dael> fremy: Not a strong preference, but I think dot is a bit nices. Easier to search with a dot then with a space.<br>
&lt;dael> astearns: You mena searching for all nested layers?<br>
&lt;dael> fremy: Yeah.<br>
&lt;dael> fremy: In general I feel it's more unique to space. Not a strong opinion. I feel like dot is more useful.<br>
&lt;dael> leaverou: How about straw poll.<br>
&lt;leaverou> space<br>
&lt;TabAtkins> Period<br>
&lt;fantasai> space<br>
&lt;jensimmons> space<br>
&lt;dael> astearns: IRC straw poll.<br>
&lt;futhark> period<br>
&lt;faceless2> period<br>
&lt;JonathanNeal> period<br>
&lt;argyle> period<br>
&lt;dholbert> period<br>
&lt;fremy> period<br>
&lt;florian> space<br>
&lt;bradk> Period<br>
&lt;dlibby> period<br>
&lt;rachelandrew> space<br>
&lt;dael> astearns: From that it looks like we're learning toward period<br>
&lt;dael> astearns: 8 to 6<br>
&lt;dael> leaverou: Not exactly consensus<br>
&lt;dael> TabAtkins: 9 to 5 I think. Not consensus. But changing to less popular might be premature.<br>
&lt;dael> astearns: Spec uses dot?<br>
&lt;dael> many: yeah<br>
&lt;dael> fantasai: Then we'd have to put in work to make periods work.<br>
&lt;JonathanNeal> Not that it should matter, but syntactically, I think a period is easier than a space.<br>
&lt;argyle> https://www.irccloud.com/pastebin/fbQB8Xeq/<br>
&lt;dael> florian: Agree it's more awkward to spec, but that's not the main concern<br>
&lt;dael> astearns: No consensus. Leave this one open and leave spec as is for now?<br>
&lt;dael> fantasai: Leave issue open and collect feedback<br>
&lt;dael> astearns: Nice to close issues, but I don't think we have consensus. We're down to space or period, though<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5791#issuecomment-768467740 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 27 January 2021 18:01:51 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:25 UTC