1817125 - Only ICC profile from main display are respected on Windows

Status: NEW

(Core :: Graphics: Color Management, defect, P3)

Description

[shine_5402]

Attachment: Color management result between two broswers

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/110.0

Steps to reproduce:

Both on 110.0(Release) and 112.0a1(Nightly) have this issue, the latter has used a whole new profile.

I have two displays with different color gamut, one for sRGB and one for DCI-P3. The latter have calibrated with DisplayCAL and have a proper icc profile in use. The sRGB one is set as my main display in Display Settings.

All color management options in about:config are setting to default.

I'm using https://cameratico.com/tools/web-browser-color-management-test/ to test color management.

Actual results:

Firefox renders these images as same color, while Google Chrome rendering them correctly mapped. When I set my DCI-P3 display as main display and restart Firefox, however, Firefox will render them correctly. (See attachment for more info).
Btw, Chrome will also switch icc profile automatically when dragging between displays, while Firefox seems only fetch it once on start... So even I've changed my main display as DCI-P3 one, it will make all window on sRGB one lost their saturation.
This behavior will cause contents on my DCI-P3 display looks over saturated, and it's definity frustrating to see.

Expected results:

ICC profiles should be respected on display bias and should be refetched while dragging between displays.

Comment 1

[shine_5402]

Attachment: Firefox color management issue

Comment 2

[shine_5402]

I've found bug 677077, but it's not updated since 11 years ago from Firefox 8 era (wow..), I think it's worth to open a new ticket since a lot has changed since then definitely. But there may be some useful info here too I guess?

Comment 3

[Teodor Tanasoaia [:teoxoy]]

Kelsey, I think you've been doing some work on color related tasks.
What do you think we should do with this one?

Comment 4

[Kelsey Gilbert [:jgilbert]]

This is known, we feel bad about it, but we haven't been able to get around to fixing it yet.

Comment 5

[shine_5402]

Can understand that. Btw, something interesting happend so I think it's worth to share it here. It seems like that Windows 11 will rolled out a new feature that provide auto color management on OS side. It's currently in Dev channel for users (though devs seems can opt in manully by registry hacks in current Release).

Reference from dev log:
"With ACM, apps that don’t explicitly target a wider color gamut (or HDR) get mapped consistently into sRGB. Apps that explicitly do color management using ICM/WCS color management APIs can still target the display’s native gamut (see below for legacy ICC compatibility), and apps written to the latest advanced color APIs can mix and match wide gamut content with sRGB content."

Urls regrading this new feature:
https://devblogs.microsoft.com/directx/auto-color-management/
https://support.microsoft.com/en-us/windows/auto-color-management-in-windows-11-64a4de7f-9c93-43ec-bdf1-3b12ffa0870b
https://learn.microsoft.com/en-us/windows/win32/direct3darticles/high-dynamic-range