- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 Oct 2022 18:07:02 +0000
- To: public-css-archive@w3.org
>> Note, tho, that this will slightly tie our hands in the future - we'll never be able to change the property syntax to start with a non-ident (like doing additive CSS by writing +transform: ... or something). This probably isn't a huge deal, but it is definitely a forwards-compat/language evolution issue to worry about. > > Seems like a pretty significant limitation to introduce. It's probably not, I think. For one, we don't actually have any plans to do anything like that, so any concerns would be purely theoretical; this isn't a syntax space we've ever played in or planned to. For two, for the same reason I have to be careful in writing the syntax spec algo (to avoid accidentally switching into "rule mode" when someone just used an ascii char to "comment out" a property), we'd have to be *extremely* careful to avoid accidentally turning currently-invalid code into correct code with an unintended meaning. More than likely we'd just avoid this altogether and stick with putting new syntax between the property name and the colon instead, which is also compatible with this Nesting syntax change. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7834#issuecomment-1275083360 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 October 2022 18:07:05 UTC