- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Oct 2018 08:04:38 +0000
- To: public-css-archive@w3.org
I was under the impression that `rgb(400, 0, 0)` is first clipped to `rgb(255, 0, 0)` and then that might be further clipped if the device gamut is smaller than sRGB (which was common when CSS Color 3 was authored, e.g. the 2013 MacBook Air gamut is around 62% of sRGB, and that's not super long ago!). This seems to be on par with what Chrome and Safari are doing ([test](http://dabblet.com/gist/19f015c5a93704c1328dbdaff01e837a)), while Gecko erroneously treats colors as being specified in device RGB and not sRGB (it still clips to 255, but in this case the opposite would be outside the device gamut). -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3187#issuecomment-430141107 using your GitHub account
Received on Tuesday, 16 October 2018 08:04:39 UTC