- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 12 Jan 2023 19:36:10 +0000
- To: public-css-archive@w3.org
> A problem I have with the "it's only an error recovery problem" approach, is that once something new gets added to selectors or properties, it's closed off forever in use for the other case. Note that I *explicitly addressed this case* in [my earlier comment](https://github.com/w3c/csswg-drafts/issues/8249#issuecomment-1379357471), even before I started talking about the error-recovery case: > For things that are currently valid, we are indeed closing the door on options. With the current spec, we cannot allow a declaration to start with +, for example, as that's a valid relative selector. (At least, not without paying a lookahead tax that we're currently rejecting.) We cannot start a selector with an ident. As I've said in previous threads, tho, starting a declaration with a symbol is already very likely off the table, given the prevalence of people using a random ascii symbol to "comment out" a property. So in practice we're closing the door on very little new space that wasn't already verboten. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8249#issuecomment-1380912319 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 12 January 2023 19:36:12 UTC