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!

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

Learn More

Firefox Color Management/Profile Not Being Used

  • 2 réponses
  • 0 a ce problème
  • 37 vues
  • Dernière réponse par 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?

Solution choisie

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.

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (2)

more options

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

more options

Solution choisie

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.