I think there may be a regression in this as untagged imagery isn’t assumed to be sRGB in Firefox 77 (20200527121107) & 78.0a1 (20200528032513) on Windows 10 with gfx.color_management.mode set to 1. I’m sure it was always working. Please let me know if it’s preferable to open a new bug or if it’s a known (temporary) issue (maybe related to this?). I’ve tried all kinds of ICC display profiles which work in eg Chrome or Photoshop.

Steps to reproduce:
Preferably on a wide gamut monitor (but any straying from sRGB will do), display the same image untagged and tagged with sRGB profile next to each other. Alternatively visit https://www.theguardian.com/uk (where images are tagged) and https://www.nytimes.com/ (where they are not) and compare how they look in Firefox and eg Chrome.

(In reply to Jeff Muizelaar [:jrmuizel] from comment #1)

Setting gfx.color_management.mode to 1 should do this.

See http://kb.mozillazine.org/Gfx.color_management.mode

Hello, Jeff, Andrew (sorry for tagging). This doesn’t seem to work for me (see above comment). Can you reproduce? Should I open a new bug?

Details for the above: Win 10 1909 (18363.836), NVidia RTX 2070 Driver 446.14.

(In reply to paperboyo from comment #5)

This doesn’t seem to work for me (see above comment). Can you reproduce? Should I open a new bug?

That seems to be a regression in FF77, I filed an issue.: https://bugzilla.mozilla.org/show_bug.cgi?id=1643417

Thank you, Nicos!

jrmuizel, after our conversation on Friday, I believe this bug should be reopened.

To recap the situation today:

• Most displays today are now wide gamut; sRGB displays are becoming increasingly rare. This means all untagged images are displayed incorrectly.
• To get consistent accurate colour, every image needs to attach an ICC profile that is ~0.5KiB just so that Firefox hits the colour correct code path. This has both performance and bandwidth implications and adds up tremendously at (CDN) scale.

A good test case can be found here: https://kornel.ski/en/color

We talked about this today in our daily meeting and agreed that this is the right thing to do. I added two dependencies that we'll need to fix first, but we should be able to do this soon.