Open Bug 1246976 Opened 5 years ago Updated 3 years ago
.color _management .mode=1 does not have any effect when hardware acceleration is on
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.103 Safari/537.36 Steps to reproduce: You need a wide-gamut display (e.g. AdobeRGB or DCI-P3) running in wide-gamut mode (e.g. iMac Retina 5K, 27-inch, Late 2015). In Firefox, set gfx.color_management.mode=1, and also set gfx.color_management.display_profile to the .icc profile used by the display. Look at any website using CSS colors or untagged images (any website, really) in Firefox (with hardware acceleration *ON*) and Safari (on OS X). Also compare the rendering between Firefox with hardware acceleration on, and off. Actual results: Firefox with hardware acceleration on renders the colors incorrectly. It stretches them past the sRGB color space making everything look extra-saturated and radioactive. Expected results: CSS colors and untagged images should be rendered by interpreting them as sRGB. This is the case with the latest Safari version (on OS X), and also in Firefox with hardware acceleration off. Only when hardware acceleration is on, there is a problem.
No update. Our Mac color management story is currently in a bad place but the graphics team has chosen to spend its resources on Quantum Render, which will hopefully also make it easier to get proper color management eventually.
4 years ago
Priority: -- → P3
You need to log in before you can comment on or make changes to this bug.