1662343 - Wrong color management on background-color transition with wide gamut display

Status: UNCONFIRMED

(Core :: Graphics: Color Management, defect)

Description

[Matías Minevitz]

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

Steps to reproduce:

My display is a Dell U2410 with AdobeRGB color profile.
Since it's a wide gamut display and I don't want the colors to look oversaturated/vibrant, I'm using this options:

• gfx.color_management.mode: 1
• gfx.color_management.enablev4: true

I followed this guide: https://cameratico.com/color-management/firefox/
The test is OK: https://cameratico.com/tools/web-browser-color-management-test/

Now CSS elements are in sRGB.

• Create an HTML element with a background-color (e.g. #28a745).
• Add a transition (e.g. transition: background-color 0.5s ease-in-out;).
• Change the background-color on hover (e.g. #218838).

Example: https://jsfiddle.net/azeos/1ojtvqwu/

Actual results:

All the colors displayed through the duration of the transition are oversaturated, not in sRGB.
If you remove the transition, both colors are displayed correctly.

This didn't happen in v79 and prior. I'm seeing this behavior with v80 and v82.0a1.

Expected results:

The transition property shouldn't affect the color management of the background element.

This doesn't happen with the "color" property.

Comment 1

[Florencia Di Ciocco, NI to vbalducci]

Hi Matias,

Thanks for all of the data and example. I was unable to reproduce this issue on Windows 10 FF Release 80.0.1 (64-bit), FF Nightly 79.0a1 (2020-06-04) (64-bit) and FF Nightly 82.0a1 (2020-09-07) (64-bit). But maybe you can provide me with a bit more info.

Does this issue occur with a fresh profile? you can find the steps here: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles?redirectlocale=en-US&redirectslug=Managing-profiles#w_starting-the-profile-manager

Can you please download Firefox Nightly from here: https://nightly.mozilla.org/ and retest the problem and see if the issue still occurs there as well?

If after doing this you can still reproduce the bug, could you send me a screenshot or a video of the bug? That always helps a lot.

Thanks in advance, Flor.

Comment 2

[Matías Minevitz]

Attachment: Video showing the bug on Firefox Nightly v82.0a1

Comment 3

[Matías Minevitz]

Attachment: Video showing the correct behavior on Chrome

Comment 4

[Matías Minevitz]

One thing I forgot to mention (can I edit my first comment?), this only happens if I have an "Adobe RGB" ICC color profile active on Windows. If I change it to sRGB (and reboot the PC or the session), since I no longer see the difference between the ProPhotoRGB and the sRGB image, the bug isn't there.

So, you need a display capable of showing more colors than sRGB and a ICC profile bigger than sRGB. If you see the difference between the ProPhotoRGB and the sRGB images, the bug is there when you change the "color_management" values.

Flor,
I tried with a clean profile on Firefox and with the latest Nightly, same results. The video was recorded with Nightly v82.0a1.

Comment 5

[Matías Minevitz]

I tried several Nightly builds and the last one that works correctly is "Nightly 74.0a1 (2020-02-10)", which (I think) it's odd, because I don't remember having any problem with Firefox until v80.

Just in case, I'm on Windows 10 64bits 2004 (19041.450).

Comment 6

[Florencia Di Ciocco, NI to vbalducci]

(In reply to Matías Minevitz from comment #4)

One thing I forgot to mention (can I edit my first comment?), this only happens if I have an "Adobe RGB" ICC color profile active on Windows.

Thanks for clarifying. Yes, I think I can't even see the saturation on your video. Yes, you can edit your first comment but it's not really necessary.

So since I can't reproduce the bug since I don't have an adove profile I've chosen a component for this bug in hope that someone with more expertise may look at it. We'll await their answer. If you consider that there's another component that's more proper for this case you may change it.

Regards, Flor.

Comment 7

[Matías Minevitz]

This is still relevant on Firefox 97.