- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Feb 2025 01:19:59 +0000
- To: public-css-archive@w3.org
That example isn't one color stop, tho - it's two color stops (two positions with one color, defining two stops). You say "many sites" are relying on this to generate rainbows, but I don't actually see rainbows very much in practice on the web. Is this just a cute CSS trick that has gotten some shares, or do we have evidence it's *actually* used in a non-trivial number of sites (and, ideally, have evidence that rendering them as a solid color would actually harm the rendering, rather than just *change* the rendering)? That said, I'm not strongly *opposed* to specifying that we always add one additional color stop at the beginning/end of the list, placed either at 0%/100% or on top of the existing first/last color stop if they're beyond the 0-100% range, and with the same color as the first/last stop. If this does indeed look to be web-required, that's acceptable, but I'd prefer to avoid it if we can, and just fix the browser bugs. ------- As an aside, we should also probably think about exactly what behavior we *do* want between a double-position stop like that. Double-position stops were added to make it easy to generate solid-color strips in a gradient without having to repeat your color; I suspect that people might expect that to remain true even if they're doing longer-hue interpolation otherwise. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11381#issuecomment-2655216286 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 13 February 2025 01:20:00 UTC