Regression: Colour management no longer working
Categories
(Core :: Graphics: Color Management, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr102 | --- | unaffected |
firefox107 | --- | verified |
firefox108 | --- | verified |
firefox109 | --- | verified |
People
(Reporter: colinlee10, Assigned: jrmuizel)
References
(Regression)
Details
(Keywords: regression)
Attachments
(3 files)
52.55 KB,
image/png
|
Details | |
944.10 KB,
application/octet-stream
|
Details | |
48 bytes,
text/x-phabricator-request
|
diannaS
:
approval-mozilla-beta+
dmeehan
:
approval-mozilla-release+
|
Details | Review |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:107.0) Gecko/20100101 Firefox/107.0
Steps to reproduce:
- Build Firefox from nightly or beta. I used 107.0b10 (64-bit)
- Apply attached ICC profile in Windows colour management
- Try a color management test after restarting the browser (e.g by using https://cameratico.com/tools/web-browser-color-management-test/, or just comparing to earlier Firefox version with gfx.color_management.mode = 1)
This ICC profile was exported by DisplayCal with standard settings after monitor profiling.
I believe this is the regression point. Reverting this change restores colour management:
https://bugzilla.mozilla.org/show_bug.cgi?id=1795045
See attached screenshots from https://cameratico.com/tools/web-browser-color-management-test/ for comparison between browsers.
Actual results:
Colour management is not visible - images appear oversaturated on wide gamut monitor. Tagged images do not have changed colors
Expected results:
Output images should have colour management applied.
Reporter | ||
Comment 1•2 years ago
|
||
Comment 2•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Graphics: Color Management' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 3•2 years ago
|
||
:jrmuizel, since you are the author of the regressor, bug 1795045, could you take a look? Also, could you set the severity field?
For more information, please visit auto_nag documentation.
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 4•2 years ago
|
||
It seems like Chrome allows this and it's relatively common.
We don't have a good reason to continue blocking these profiles.
Updated•2 years ago
|
Comment 6•2 years ago
|
||
bugherder |
Reporter | ||
Comment 7•2 years ago
|
||
Thanks. Verified fix on my end
Comment 8•2 years ago
|
||
Set release status flags based on info from the regressing bug 1795045
Comment 9•2 years ago
|
||
I assume you're going to want this in a dot release, so go ahead and nominate for Beta & Release approval when you get a chance. It grafts cleanly.
Assignee | ||
Comment 10•2 years ago
|
||
colinlee10, did you have gfx.color_management.enablev4 set to true?
Assignee | ||
Comment 12•2 years ago
|
||
Comment on attachment 9303350 [details]
Bug 1799391. Allow negative XYZ on non-macOS.
Beta/Release Uplift Approval Request
- User impact if declined: Color management will not work for some people with negative XYZ in their profiles
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): We've been shipping this change on macOS for many year.
- String changes made/needed:
- Is Android affected?: Yes
Comment 13•2 years ago
|
||
Comment on attachment 9303350 [details]
Bug 1799391. Allow negative XYZ on non-macOS.
Approved for 108.0b4
Comment 14•2 years ago
|
||
bugherder uplift |
Comment 15•2 years ago
|
||
:jrmuizel could you add a release uplift request on this when ready?
Would like to consider including this in the planned dot release
Updated•2 years ago
|
Assignee | ||
Comment 16•2 years ago
|
||
Comment on attachment 9303350 [details]
Bug 1799391. Allow negative XYZ on non-macOS.
Beta/Release Uplift Approval Request
- User impact if declined: Users that have set gfx.color_management.enablev4=true may get broken color management on Windows and Linux
- Is this code covered by automated tests?: No
- Has the fix been verified in Nightly?: Yes
- Needs manual test from QE?: Yes
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): This will cause us to accept profiles that we previously rejected. As far as we know that's ok.
- String changes made/needed:
- Is Android affected?: Yes
Assignee | ||
Comment 17•2 years ago
|
||
https://www.reddit.com/r/firefox/comments/z1t28j/color_management_not_working_after_microsoft/ sounds like it might be another user running into this issue in 107.
Comment 18•2 years ago
•
|
||
Reproduced the bug as observed in screenshot from description, on Beta 108.0b2 on Windows 10. Also, on affected build, there are no changes on colors when set gfx.color_management.mode = 1 (default is 2).
I can confirm that bug is fixed on Beta 108.0b5 and latest Nightly build ID 20221122094606, on Windows 10 and Ubuntu 18.04 x64
Updated•2 years ago
|
Comment 19•2 years ago
|
||
Comment on attachment 9303350 [details]
Bug 1799391. Allow negative XYZ on non-macOS.
Approved for 107.0.1
Comment 20•2 years ago
|
||
bugherder uplift |
Comment 21•2 years ago
|
||
Verified as fixed on RC 107.0.1 on Windows 10 and Ubuntu 18.04 x64.
Description
•