No, chrome is now respecting color profiles provided by the operating system.

Please look at this document for information on how to adjust the way chrome makes use of color profiles: https://docs.google.com/document/d/1jMokB_OBkZVELu22li8vnHxAUoL1eGnLedP-1Gttv40/edit?usp=sharing

If your problems persist, attach the color profile you are using as it might be revealing bugs in our implementation.

I'd like to think Chromium uses lcms2, so that we're all able to leverage the improvement made there. If there are browser specific performance requirements, again they should go into lcms2 were that work can be used elsewhere. Color management is sufficiently complex there is no good reason to be reinventing the wheel with different CMS engines, and inevitably repeating history with piles of bugs that need to be fixed in a new implementation that have already been fixed in the existing one.

> No, chrome is now respecting color profiles provided by the operating system.

I'm afraid that there is double color correction is done, one by gnome color management and one by chrome, can we have chrome detect that my fedora is already doing color correction and stop its own correction.

https://help.gnome.org/users/gnome-help/stable/color-whyimportant.html.en

http://libregraphicsworld.org/blog/entry/richard-hughes-on-color-management-in-linux-and-gnome

> Color management is sufficiently complex there is no good reason to be reinventing the wheel with different CMS engines

totally agree

> If your problems persist, attach the color profile you are using as it might be revealing bugs in our implementation.

for now can we have a build/compile-time flag to disable this, to let fedora do the color correction on its own when using chromium shipped by fedora, until we figure our how to properly fix this

Thank you for providing more feedback. Adding requester "schenney@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

> If your problems persist,

my problem is that I have two color correction, one by gnome and one by chrome, and clearly the blue I see in firefox is the right blue.

Deleted: edid-807c1c980c34dbcb5c948249ae091f4b.icc 1.3 KB

edid-807c1c980c34dbcb5c948249ae091f4b.icc 1.3 KB Download

Deleted: Screenshot from 2017-11-16 11-58-42.png 41.5 KB

	Screenshot from 2017-11-16 11-58-42.png 41.5 KB View Download

I very strongly suspect that you have installed a profile that you do not actually want -- that profile attached is extremely purple.

I have yet to see Gnome cause anything to be rendered differently due to color profiles being installed (except for Eye of Gnome) -- it seems to mostly just ignore the profile.

If you're convinced that Chrome is not treating your profile correctly, please see the last section in this document about forcing Chrome to use an sRGB profile in about:flags
https://docs.google.com/document/d/1jMokB_OBkZVELu22li8vnHxAUoL1eGnLedP-1Gttv40/edit?usp=sharing

> I very strongly suspect that you have installed a profile that you do not actually want -- that profile attached is extremely purple.

I did not define this color profile, it was enabled by fedora
and it works well for firefox, gnome, ...etc.

the problem is only visible in chrome/chromium

in the past gimp used to have that problem, but it was solved.

when I disabled color management in chrome, the problem was fixed.

I guess the problem is that color correction is done twice, once by GTK3 or another by chrome


how to know if my profile is wrong?

The NextAction date has arrived: 2017-11-27

what should be do now?

The ping was due to the original request for feedback. Sorry we did not remove it when the bug was marked as WontFix. There will be no further action on our part.

Please read this document that describes your problem and the solutions you can apply on your end
https://docs.google.com/document/d/1jMokB_OBkZVELu22li8vnHxAUoL1eGnLedP-1Gttv40/edit?usp=sharing