- From: Tab Atkins Jr. via GitHub <noreply@w3.org>
- Date: Wed, 06 May 2026 16:10:56 +0000
- To: public-css-archive@w3.org
We indeed already discussed making the `none` keyword generically an image, and it's unworkable. This needs to compute to something else. I don't have much of an opinion on *how* we represent the transparent image. `image(transparent)` is probably the most straightforward way, except that no one implements `image()` yet. I think we should go ahead and just punt all the non-color uses of `image()` to the future and just ship the `image(<color>)` version; beyond this use-case, it's just generally useful for other things (as evidenced by people using `linear-gradient()` for this use-case). `image(none)` doesn't seem necessary, since `image(transparent)` already works per spec. (But I'm not strongly opposed if someone has a good reason for it.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13866#issuecomment-4389956719 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 May 2026 16:10:57 UTC