- From: Michael C. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 11 Nov 2021 22:26:58 +0000
- To: public-css-archive@w3.org
> My concern here is about (a) learnability and (b) extensibility to other contexts. The more things stick to "standard"/pre-existing CSS syntax constructs, the easier it is to learn and explain; every diversion from the CSS standard practice means another oddity for authors to learn and remember. As well, the more things stick to standard practice, the more likely we can use it in other CSS contexts without having to do anything special; we wouldn't even need to _think_ about mixing it in syntactically, it will Just Work.
To be fair, the closest proposal of all of these to "CSS standard practice" is the one that copies the pattern established by things such as `@keyframes { ... }` and `@media () { ... }`. It's the second proposal in my original post at the very start of the thread. It just adds an extra level of indentation... as do both `@keyframes` and `@media`, really. ¯\\\_(ツ)_/¯
--
GitHub Notification of comment by proimage
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4748#issuecomment-966670174 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 11 November 2021 22:27:00 UTC