- From: Simon Fraser via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Mar 2022 05:06:07 +0000
- To: public-css-archive@w3.org
smfr has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-color] [filter-effects] Should no-op filters produce different output from no filter? == The [filter property](https://drafts.fxtf.org/filter-effects/#FilterProperty) states that "Functions must operate in the sRGB color space". This implies that all the input colors to filters, like display-p3 colors and images with P3 color profiles get flattened to sRGB before filter processing. This has the unfortunate side effect that the results of `filter: none` and `filter: saturate(1)` are different when the filtered content contains P3 colors, and that authors can't apply nice filter effects to P3 images while retaining out-of-sRGB colors. Chrome appears to not follow this spec text precisely, and seems (on macOS at least) to apply filters in some extended sRGB colorspace (tested on iMac Pro with DisplayP3 display). Testcase: https://codepen.io/smfr/pen/PoOVmPX cc @svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7100 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 March 2022 05:06:09 UTC