You must have a wide-color-gamut compatible monitor in order for the test to even be possible. Most laptops and desktops do not.

Safari on my iPhone X passes.

And have properly set up colour management working, which on Windows is close to zero percent probability.

This also ignores the shortcuts that Chrome and other browsers have taken on their road to colour management.

> And have properly set up colour management working, which on Windows is close to zero percent probability.

Maybe surprising to some, but Windows actually supports HDR10 (which includes "wide-gamut" color) better than other OSes. You can, for example, play HDR10 video games with a connected HDR-capable monitor. It might be thanks to MS's Xbox platform.

Chrome vs Firefox on the Pixel 2 https://i.imgur.com/kwirB6C.png

I am confused about why I can see this screenshot since I am not on a wide gamut monitor. Is firefox doing a weird conversion or the screenshotting tool?

My (probably flawed) understanding was that wide colors means there's more than 8 bits. So stuff that would be say rgb(254.5, 0, 0) would now be distinguishable from rgb(255, 0, 0)? If you screenshotted it back to 8 bit you would just lose the extra bits and I expected to still see a red square? Or is that not how it works?

Yes flawed. If you have a bitmap that's using a wide color space (e. g. P3/OLED) and it has a green (0,1,0) pixel then that's referring to a color than an LCD display cannot possibly show. 0,1,0 on an LCD is a less saturated green. The OS changes color values to try to make things look as much as expected as possible, and that results in color clipping. A screenshot saves images as sRGB and so no remapping is done upon display.

Firefox on a Galaxy S8 works. I wonder what the difference could be between two browsers on the same phone?

That's what the article is about: Apps need to use Android APIs correctly to display color accurately.

So Google Chrome running on Google Android doesn't use the correct Android APIs but Firefox does? Why is Chrome "the standard" again?

I just set the Chrome flag to force the display profile and was able to see the image on my Pixel 3a. The default profile will not show it.

So Chrome is using the APIs, but actually using that profile is still behind a feature flag, it seems.

Edit: I just tried it in Firefox and the log is much clearer. This makes me think that Firefox is doing something to change the image before displaying it, which is why it "works" there.

On Chrome, the image was incredibly faint.

> Why is Chrome "the standard" again?

It has no adblocker.

A lot of variables involved. For me Win 10 17134, with an NVidia GTX 960, over displayport to Dell U2417H, I can see the two colors in Chrome and Firefox. I can't see the color difference in Microsoft Edge. The ICC Profile for the monitor was automatically loaded by Windows. Everything is 32 bit.

I think the ICC profile is the only reason I can see it and it isn't a very strong difference on my monitor.

Edit: When I say 32bit, I mean 8 bit per RGB channel/24 bit "True Color"

Do you have a HDR display? Have you enabled Wide Colour Gamut?