搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Color Management Problem - Wide Gamut Monitor and Firefox 77.01

more options

I recently had an automatic upgrade to Firefox 77.01 and noticed my monitor color saturation changed. I use a NEC P221 wide gamut monitor, and I'm aware of the over-saturation issues with wide gamut monitors. I'm on a 2011 Mac Mini using High Sierra 10.13.6. In the past when this issue has come up, I'd use the about:config command to adjust Firefox's color management settings. When I tried adjusting it for the new upgrade, I haven't been able to correct the problem. I tried using different values for the settings and also tried supplying the exact monitor profile name pathway to replace the "gfx.color_management.display_profile" setting.

I’ve attached a screen shot of my current settings. Any help/advice/suggestions on how to fix this problem will be greatly appreciated!

David

I recently had an automatic upgrade to Firefox 77.01 and noticed my monitor color saturation changed. I use a NEC P221 wide gamut monitor, and I'm aware of the over-saturation issues with wide gamut monitors. I'm on a 2011 Mac Mini using High Sierra 10.13.6. In the past when this issue has come up, I'd use the about:config command to adjust Firefox's color management settings. When I tried adjusting it for the new upgrade, I haven't been able to correct the problem. I tried using different values for the settings and also tried supplying the exact monitor profile name pathway to replace the "gfx.color_management.display_profile" setting. I’ve attached a screen shot of my current settings. Any help/advice/suggestions on how to fix this problem will be greatly appreciated! David
已附加屏幕截图

所有回复 (3)

more options

Hi davidmschrader, please ignore the spam message with a phone number -- that's not official and we don't know what they will do to your system if you engage.

more options

Hello,

Ignore becky409's post, It's Spam.

In your product, are you assigning a color space?

I think by default Firefox will use the sRGB color space for images, but if a color space is designated, it may behave somewhat differently.

You could try adjusting Firefox's color management settings. This is an old write-up, but I haven't heard about any changes since then:

By default, Firefox will try to color manage tagged images (JPEGs and PNGs). You can review and experiment with the following preferences to see whether one of them is causing the problem:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.

(2) In the search box above the list, type or paste gfx.c and pause while the list is filtered

gfx.color_management.mode - governs application of color management to images

  • 0 = off
  • 1 = on for ALL images
  • 2 = on for TAGGED images (default)

I can't recall whether you need to quit/restart Firefox before this change, or changes to the below preferences, takes effect.

gfx.color_management.display_profile - if you have created a custom monitor profile and Firefox is not using it, you can enter the path to it here.

gfx.color_management.enablev4 - double-click to toggle to true if your custom monitor profile is an ICC v4 profile

gfx.color_management.rendering_intent - whether Firefox honors or overrides the intent flag in the ICC profile, by default, overrides to Perceptual

For details, see: https://developer.mozilla.org/Firefox/Releases/3.5/ICC_color_correction_in_Firefox

Can you find a combination of settings that gives you the colors you expect? Depending on your results, and whether you are publishing these images on the web, you might need to revise how it deals with color spaces.

Hope it works. Thank You.

more options

Hi Shashank,

Thanks for your reply but I've already tried everything you've suggested. Also, you can see my current management settings by viewing my attachment from my original post. All images that I upload to my Etsy shop have embedded sRGB profiles, so those management settings should work. I read online that there's a bug with 77.01 but I thought my current settings should correct it; perhaps not.