Re: [csswg-drafts] [css-syntax-3] Allow positioned {}-block in `@property/initial-value` (#11737)

Ah, I see, since 'initial-value` isn't a custom property name, the parser will reject the value if it's got a `{}` block plus other stuff.

I'm not particularly sad about that. Allowing {} with other junk in a custom property is mostly there for back-compat. If you're registering a custom property, it's very likely to be with intent to use it for CSS stuff, where that sort of value would be completley invalid anyway. (You'd need to pair with a `syntax: "*";` anyway, meaning that if you *weren't* using it for CSS values, the only reason to register it would be to turn off inheritance, which is a super minimal use-case at that point. Just put it in some parens or something if you *really* care, so it's not top-level.)

So, I'm inclined to just leave this as no change: you cannot express certain initial values for a registered custom property, even tho they are technically syntactically valid values for the property to have.

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11737#issuecomment-2666709462 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 18 February 2025 19:18:23 UTC