- From: Romain Menke via GitHub <sysbot+gh@w3.org>
- Date: Fri, 22 Mar 2024 09:40:49 +0000
- To: public-css-archive@w3.org
I am not sure how we are misunderstanding each other here :) > I’ve explained above why you should prefer to serve wide-gamut images to users on a wide-gamut display. If you serve wide-gamut images to users not on a wide-gamut display, WebKit will color-match the images and show them in the sRGB space. However, this conversion into sRGB can be done a few ways and isn’t guaranteed to happen identically on other browsers or platforms. As a discerning Web developer or designer you will want to convert your images offline to better control what the end user will see. Also, embedding the color profile adds a little to the file size, so you might not want to send that extra data if it isn’t necessary. > The best solution is to serve a wide-gamut image when the user is on a wide-gamut display, and an sRGB image when the user is not on a wide-gamut display. This is just another case of responsive images, and is exactly what the element and media queries were designed to handle. I am reading : If you care about color accuracy then you should create tailored assets and use the media query to conditionally load the correct asset. Do not leave up to automatic color matching as it isn't guaranteed to be identical across platforms, hardware, ... Is this incorrect, if so, how? -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10055#issuecomment-2014712276 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 22 March 2024 09:40:50 UTC