Open Bug 1850716 Opened 1 year ago Updated 4 months ago

Color management [with installed display color profile] broken

Categories

(Core :: Graphics: Color Management, defect)

Desktop
Windows
defect

Tracking

()

Tracking Status
firefox-esr102 --- affected
firefox-esr115 --- affected
firefox117 --- affected
firefox118 --- affected
firefox119 --- affected

People

(Reporter: oardelean, Unassigned, NeedInfo)

References

Details

Attachments

(1 file)

Found in

  • Beta 118.0b2;

Affected versions

  • Beta 118.0b2;
  • Nightly 119.0a1;

Tested platforms

  • Windows 10/11;

Affected platforms

  • Windows 10/11;

Unaffected platforms

  • macOS, Linux;

Preconditions

  • Install a deliberately-wrong color profile for the (primary/in-use) display. This one can be used - IdentityRGB-elle-V4-g10.icc
  • To make sure this profile is in use access Color Management in Windows, select Advanced and from Device profile dropdown select -> IdentityRGB-elle-V4-g10.icc

Steps to reproduce

  1. Launch Firefox and alongside have another browser opened (ex. Chrome)
  2. Restart both browsers.
  3. Access this image on both browsers and compare them.

Expected result

  • The colors on both are estompated according to the active profile.

Actual result

  • On Firefox the colors seem to be oversaturated compared to Chrome.

Regression range

  • Will look for one ASAP.

:oardelean, if you think that's a regression, could you try to find a regression range using for example mozregression?

QA Whiteboard: regressionwindow-wanted
QA Whiteboard: regressionwindow-wanted
QA Whiteboard: [qa-regression-triage]

This issue does not appear to be a regression considering that the same color gradient can be observed on builds as far back as Nightly v35.0a1. This might be an issue in Chrome rather than in Firefox considering that the color setting is intended to be a little off and also, the fact that the color is quite unrealistic in both browsers, but different.

QA Whiteboard: [qa-regression-triage]
Version: unspecified → Trunk

Desktop QA has been highlighting this defect as a known issue for several release cycles now, following regression testing. Kelsey, it would really help us if you set a priority on this bug — it will give us clarity on whether this issue is still worth mentioning in future test reports.

Flags: needinfo?(jgilbert)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: