1643242 - regression in FF77: gfx.color_management settings are ignored

Status: RESOLVED DUPLICATE of bug 1639584

(Core :: Graphics: Color Management, defect)

Description

[spacespencer]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:77.0) Gecko/20100101 Firefox/77.0

Steps to reproduce:

setting gfx.color_management via about:config to 1 has no effect

Actual results:

colors are super over saturated and extremely hot, RGB not being displayed properly

Expected results:

color profiles really ought to work

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

Comment 2

[Sotaro Ikeda [:sotaro]]

: aosmond, can you comment to the bug?

Comment 3

[Bob M]

I have found this to be the case as well, but I think the problem is slightly more nuanced than the entire thing being broken.

Color management is working for me on some pages, but not on others. It seems like simple images (IMG tags) are going through the color management system, but images that get put onto the page in other ways (scripts I guess?) no longer are -- for instance pretty much every image on YouTube, and thumbnails & show/movie artwork on a Plex server.

Comment 4

[leitec]

I believe this is related to https://bugzilla.mozilla.org/show_bug.cgi?id=1631615,

We have too aggressively color manage images which content authors did not intend to be color managed; if storing data like windy.com, it is hard to predict what would happen; it is also a webcompat issue with Chrome

I can't speak to the actual bug seen on windy.com, but the conclusion that FF too aggressively CM's images does not seem to be correct. If I read the sRGB spec correctly (the "Standard Color Space in Practice, Browsing Scenarios" section), assuming sRGB on untagged content is the recommended approach:

Image not in sRGB, does not have an embedded ICC profile, and system has a monitor/output device ICC profile

Since the image has no ICC profile, it is assumed to be in the sRGB color space. In this scenario, the resulting image will be consistent across devices; however it could be different from the original image.

As far as I can tell, Chrome does indeed fall back to sRGB on untagged content. Chrome and FF <77 appear correct on a wide-gamut monitor whereas Firefox 77 does not even with color_management=1. (I am aware that Chrome's CM is flawed, but it is "correct enough" on this monitor) I am on Linux so there is no OS-level color management involved.