https://bugs.kde.org/show_bug.cgi?id=367832
--- Comment #35 from Tyson Tan <tysont...@gmail.com> --- (In reply to Dmitry Kazakov from comment #34) > Just a side note: if we set srgb png tag (without embedding the profile), > Firefox still renders incorrectly (at least it used to have, because saving > this tag is commented out in the code). After some further research, this problem appears to be so much more complicated...so instead of advising a change, it's wiser for me to just share what I've found, and discuss about them. ### How Firefox does color management now When I tested it in Firefox 70.0.1 (Win10/Linux), it would not do color management unless the picture has a color space assigned to it, being sRGB or not. This is the default behavior. By setting about:config -> gfx.color_management.mode to 1, you can force Firefox to color manage all untagged picture as if they are in sRGB. But not all picture uses sRGB, so this can introduce issues. To be honest, I don't think Firefox had "changed" its behavior. Most applications behave the same way, and many of them do not color manage PNGs with Alpha channel. It was more likely to be me who got it wrong in the past. Now I can test with a wide-gamut display and a sRGB display side-by-side, and I've also studied proper color management workflow, it's most likely that I was finally doing it correctly in Comment #32 and Comment #33. ### When non-sRGB color spaces are taken into context When talking about Krita's default PNG exporting settings -- since we check "Force convert to sRGB" by default, it makes sense to also check "Embed sRGB profile" and uncheck "Store Alpha channel" -- this way we can ensure 100% compatiblity with sRGB. In case of a wide-gamut display, the picture will be rendered correctly without tweaking Firefox (or other applications). In case of sRGB displays, it doesn't make any difference. However, the problem is obvious -- "Embed sRGB profile" makes no sense if we are saving a non-sRGB PNG. And it immediately brings up some more questions: 1) Does PNG force us to use sRGB color space? 2) Can Krita embed the working file's profile in the future? 3) When rec. 2020 color space became widely adopted, do we add new settings accordingly? So long as most people are using sRGB displays, this is not yet a big issue. But the industry is now moving towards a wider color space, the majority of mid-high tier users are going to experience over-saturated color if we do nothing. Maybe it's time to discuss whether we sacrifice a larger color space for safe color rendering, or something else we can do as a workaround. -- You are receiving this mail because: You are watching all bug changes.
