sRGB color shift in Firefox - (possibly) SOLVED! - Please help me find holes in this.

eatbrian  wrote Does it seem like a good idea to edit in sRGB and proof it in Wide Gamut to find a balance between the 2?   And is it safe to assume that most modern monitors/screens will display wide gamut?

No, absolutely not! There's no reason to add to the confusion.

Working with wide gamut displays is totally unproblematic and streamlined, as long as you always use color managed applications. For web it's certainly no problem, as color managed web browsers have been around for many years.

There is usually an sRGB emulation that is easily accessible if you have to use applications without color management.

Wide gamut displays have always been a very small high-end niche. People who purchase these units are usually well aware of what they're getting into, and take the necessary precautions. That changed somewhat a year or two ago, when Apple started to ship iMac and MBP with wide gamut displays as standard.

Predictably, Apple couldn't use the existing wide gamut panels that the rest of the world had been happily using for years. They had to come up with their own variety, DCI-P3, which in reality is a cinema projection standard. But functionally that doesn't matter much. The important fact is that all panels that don't match sRGB always need full color management to display correctly.

https://forums.adobe.com/people/Test+Screen+Name  wrote if you are designing for the web you should not be using a wide gamut monitor in the first place.

Actually a wide gamut monitor can be your best friend for web work - if you understand what a wide gamut monitor is and what the implications are.

For one thing, it gives you immediate color management feedback. You can see right away if something's color managed or not.

Secondly, a wide gamut monitor covers sRGB 100%. That means sRGB emulation is usually very accurate. A standard gamut monitor can be pretty far off sRGB coverage, mainly because the primaries don't match up. Mismatched primaries cause shifts in individual colors, like blue skies.

The third advantage is more subtle. Since you have to use a color managed browser in the Firefox mode 1 configuration - assign sRGB/convert to monitor - that means you have full color management at all times. That's a fully color managed web interface, ladies and gentlemen, and you don't even need embedded profiles! No more guessing, no more "close enough".

Thank you for your time. Here is where there is confusion...

What happens here is that your files don't have an embedded color profile. Even if you embed the profile when exporting, many sites subsequently strip the profile.

Many sites? or many browsers?

Firefox is color managed as long as there is an embedded profile. At default settings, Firefox does not color manage files without an embedded profile. However, there is a setting you can enable that assigns sRGB to all untagged material. This allows the color management chain to operate again. It's known as "mode 1" as opposed to the default "mode 2".

Here is what doesn't make sense-    I edit on a calibrated monitor in PS, I save for Web - Convert to sRGB and embed profile.  The image looks perfect when opened in OSX preview, Safari and even if I send them out to a print shop that prints in the sRGB color space.  They all look exactly as they did in photoshop.

The only place they look different is in Firefox.  Without changing the firefox settings, is there something I am missing up to this point?

This simple setting in Firefox allows full color management in all scenarios. This is why Firefox is an excellent browser to use with wide gamut monitors - it will always display absolutely correctly, identical to Photoshop at all times.

I have a wide gamut monitor but I have not experienced absolute correctness at all.

Now, Photoshop. What you have just done is to disable Photoshop's color management completely. So yes, it will match a non-color managed web browser - but it's all wrong, and completely unnecessary.

Why is it wrong and unncessary?  In what situation would this create an actual problem?  Please give me one example.

Set Photoshop's Color Settings back to defaults. Set working RGB to a standard color space like sRGB or Adobe RGB, and set color management policies to "Preserve Embedded Profiles". This whole situation is very easily put right. Of course, you do need to have a good monitor profile - which is, one that accurately describes your monitor's actual, current response. A calibrator will give you that. Here's how you set Firefox to Mode 1. Type "about:config" in the address bar and refresh:

I really appreciate you helping with this.  I still see no evidence or reasonable situation where "my method" would cause problems except for someone using a really old computer or web browser??    The only issue I see and don't see a solution for is the color shifting in my images in Firefox. 

I will try changing the color management modes. The problem is that even if this does fix the problem, that most regular people will not have this setup properly on their computers before viewing my website which brings us back to the original color shift problem.  

Am I really the only photographer experiencing this?

Thanks again!

Thank you for taking the time to reply.

I have a 2012 Retina MBP - Calibrated monitor.  And also an  iMac (Retina 5K, 27-inch, Late 2015) - Also Calibrated.   The strong coloro shift in Firefox is apparent on both computers and on countless other computers I've done quick tests with.

In what type of situation might it make it worse and how can you prove it?

Respectfully

Brian