- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Dec 2022 20:03:56 +0000
- To: public-css-archive@w3.org
Also as a secondary concern, people *today* use all sorts of ASCII garbage as a "commenting" mechanism for properties. Writing `*color: red;` as a way to temporarily comment out the 'color' property happens all the time, and often ships publicly too! So, any future extensions to property syntax that try to add a glyph before the property name need to deal with the potential compat impact of this invalid CSS in the wild. (Nesting gets away with having these invalid declarations trigger style rules because the rest of the declaration won't look like a valid style rule, and we have the early exit if we see the `;` while parsing the "selector" of the rule.) In other words, the syntax space of "declarations, but we put a glyph at the beginning" is *already* pretty decently poisoned and probably a space we want to avoid. So, having Nesting consume that syntax space more explicitly doesn't actually reduce our usable options as much as it might look. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8251#issuecomment-1362029580 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 21 December 2022 20:03:57 UTC