This is to track the development of true color correct rendering.
This feature is under development behind the flag --enable-color-correct-rendering.
This rendering mode (in contrast with legacy color correct rendering in issue 667431, which is --enable-legacy-color-correct-rendering) has correctly linear interpolation of colors.
See details in
https://docs.google.com/document/d/1BMyXXTmiAragmt5ukVBIIOLDthd7JcJBgGMt-PwuTHY/edit#
The main work items for this will be
- tagging all images with a renderable color space (sRGB or linear)
- specifying
- doing color correct rendering in the compositor (including linear blending)
In the long term, this mode will need to exist side-by-side with legacy color mode. For the moment, this can be an either-or mode.

I just had the time to play around with everything and it looks like --enable-color-correct-rendering does have a big effect on my setup (macOS 10.12.2, nVidia GTX960 with WebDrivers, Dell UP2715k display (wider color gammut). Unfortunately this effect totally break up colors and makes them even more unrealistic then using chrome without any flag.
Using --enable-true-color-rendering doesn't have any visible effect compared to non-flag.

Aww having just one flag is pretty nice, as the different between "colorCorrectRendering" and "trueColorCorrectRendering" wasn´t that clear anyway.. I saw that colorCorrectRendering now enables all the features which are where enabled by trueColorCorrectRendering before!

Same as timo.wi...@gmail.com above.
When launching Chrome with the option is crashes as soon as it tries to load a page.
In Windows' Color Management settings, if I change my custom ICC profile to the
sRGB profile, or some other default one, then Chrome doesn't crash (but no color correction happens)
Chrome Version: 58.0.3029.81
Operating System: Windows NT 10.0.15063
****DO NOT CHANGE BELOW THIS LINE****
Crash ID: crash/d409d42590000000