- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Tue, 24 Mar 2026 21:07:32 +0000
- To: public-css-archive@w3.org
Thanks for the compat analysis, Lea. I agree that it's likely unsafe to have a `none` keyword be generically an `<image>`, since we use `none` in plenty of other ways and those ways sometimes combine with images. It's the sort of thing that would be a constant pain point to remember to control for; *every other* image value is grammatically unambiguous in *any* position. I don't think we need a special production just for this. `<image-or-none>` isn't any shorter or more comprehensible than `<image> | none`. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12513#issuecomment-4121365592 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 24 March 2026 21:07:33 UTC