I'm amused that chrome on Win10 does not pass their simple red logo test.
Safari on my iPhone X passes.
This also ignores the shortcuts that Chrome and other browsers have taken on their road to colour management.
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.
It has no adblocker.
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.
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?
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"