Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Pesquisar no apoio

Evite burlas no apoio. Nunca iremos solicitar que telefone ou envie uma mensagem de texto para um número de telefone ou que partilhe informações pessoais. Por favor, reporte atividades suspeitas utilizando a opção "Reportar abuso".

Saber mais

Esta discussão foi arquivada. Se precisar de ajuda, por favor, coloque uma nova questão.

Firefox Color Management/Profile Not Being Used

  • 2 respostas
  • 0 têm este problema
  • 153 visualizações
  • Última resposta por nrbelex
  • Resolvido

nrbelex
nrbelex

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?

Solução escolhida

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.

Ler esta resposta no contexto 👍 0

Todas as respostas (2)

nrbelex
nrbelex Proprietário da pergunta

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

nrbelex
nrbelex Proprietário da pergunta

Solução escolhida

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.