Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Learn More

Ova tema je arhivirana. Postavi novo pitanje ako trebaš pomoć.

Firefox Color Management/Profile Not Being Used

  • 2 odgovora
  • 0 ima ovaj problem
  • 37 prikaza
  • Posljednji odgovor od nrbelex

nrbelex
nrbelex
more options

In FF 107.0 (64-bit) on Windows 11, I'm finding that FF is suddenly not honoring my color profile, so everything looks over-saturated. I've tried using gfx.color_management.mode 1 (my typical setting) and 2 (the default), and neither seems to fix the issue. The same issue exists in a fresh profile. I'd roll back to test an earlier version of FF, but it seems that's no longer easily possible. Edge is displaying colors properly.

Any ideas or known bugs?

In FF 107.0 (64-bit) on Windows 11, I'm finding that FF is suddenly not honoring my color profile, so everything looks over-saturated. I've tried using gfx.color_management.mode 1 (my typical setting) and 2 (the default), and neither seems to fix the issue. The same issue exists in a fresh profile. I'd roll back to test an earlier version of FF, but it seems that's no longer easily possible. Edge is displaying colors properly. Any ideas or known bugs?

Izabrano rješenje

This was the result of https://bugzilla.mozilla.org/show_bug.cgi?id=1799391 and resolved when that bug was fixed in 107.0.1.

Pročitaj ovaj odgovor u kontekstu 👍 0

Svi odgovori (2)

nrbelex
nrbelex Vlasnik pitanja
more options

More info: this affects sRGB images and images with other color profiles.

nrbelex
nrbelex Vlasnik pitanja
more options

Odabrano rješenje

This was the result of https://bugzilla.mozilla.org/show_bug.cgi?id=1799391 and resolved when that bug was fixed in 107.0.1.