- From: Yehonatan Daniv via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Oct 2022 21:01:42 +0000
- To: public-css-archive@w3.org
> Conceptually, style rules would now have three parts:
>
> a selector
> a declaration block
> a style rule block (optional)
I think a big pro with this approach proposed by @fantasai & @FremyCompany is that it minimizes the extra restrictions and further "parser no-go"s we'll have to impose on future syntax, and we know how much users hate that and find that confusing.
I think, instead, it's rather another opportunity to maintain current syntax flexibility, with just a tiny compromise on nesting-syntax paradigm.
Yes, it's a slight paradigm shift, sort of Functional vs. OO, and I think that is how we should try to approach it.
I also think that with a bit more of bikeshading we can also overcome the `.a, .b & {...}` issue (I can already think of a few noisy ones 😋 )
--
GitHub Notification of comment by ydaniv
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7834#issuecomment-1282999298 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 October 2022 21:01:44 UTC