1731888 - Cached sRGB transforms can be noticeably different then ones created from embedded sRGB profiles

Status: NEW

(Core :: Graphics: Color Management, defect)

Description

[Jeff Muizelaar [:jrmuizel]]

We don't turn on v4 until after creating the cached sRGB transforms:
https://searchfox.org/mozilla-central/rev/15de05f0e6d841cbc2ac66f8dcad72ebdada47f6/gfx/thebes/gfxPlatform.cpp#2102

This can cause the cached transforms to be noticeably different then the ones created after startup because we don't use the embedded LUTs until v4 is turned on.

Comment 1

[Jeff Muizelaar [:jrmuizel]]

The right solution might be to always ignore output LUTs. They are probably too slow to be a good idea.

Comment 2

[Jon Bauman [:jbauman:]]

Wouldn't that lead to incorrect rendering when the display profile makes use of LUTs?

Comment 3

[Jeff Muizelaar [:jrmuizel]]

I believe display profiles are still required to have Tone Reproduce Curves. So the rendering may not match the LUT exactly, but hopefully won't be too far off.

My understanding is that Chrome does not use the LUTs from the display profiles.

Comment 4

[BugBot [:suhaib / :marco/ :calixte]]

The severity field is not set for this bug.
:aosmond, could you have a look please?

For more information, please visit auto_nag documentation.