- From: Simon Fraser via GitHub <sysbot+gh@w3.org>
- Date: Tue, 19 Apr 2022 16:58:09 +0000
- To: public-css-archive@w3.org
A new value for `color-interpolation-filters` seems OK, but because it would be opt-in for web developers, doesn't address my initial concerns. I'd prefer that no-op CSS filters (like `blur(0)`, `saturate(1)` etc) act like no filter is applied, which means they can't use sRGB interpolation by default. I'd prefer this for two reasons: 1. Web developers working on sRGB displays don't unintentionally clamp filtered Display-P3 assets to sRGB inside no-op filters 2. User agents can optimize away no-op filters from their rendering pipeline Doing this would require a spec change along the lines of "CSS filters operate in the current compositing colorspace" (with some handwaving because we specify that the working colorspace is sRGB but that's not what browsers do now). -- GitHub Notification of comment by smfr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7100#issuecomment-1102879576 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 19 April 2022 16:58:11 UTC