2011 iMac display I can't see the logo, but if I drag the Chrome tab over to a connected ViewSonic VA2431wm monitor from years ago, the logo shows up. Interesting.

2011 iMac doesn’t have a P3 display iirc, but ViewSonic certainly had models that could back then.

I'm on a Pixel 3. It's just solid red - no faint logo.

Odd. I'm on an iPhone XS and it's working for me.

It might be included only in the Android Q update.

Googling around shows that it might be restricted to custom apps only?

"There is one way to bypass this issue, and that is to explicitly tell Chrome to override the default provided system colour profile and just tell it the display is Display P3. This enables colour management in the app, and short of writing a custom application, is the only way to get wide colour gamut content to work on the Pixel 3."

https://www.anandtech.com/show/13474/the-google-pixel-3-revi...

Save it to your device, and open it from the Photos app. Chrome doesn't seem to like wide color, but Photos does.

So this is interesting... I did this, and it only shows up in the preview/thumbnail view. Once I click on the thumbnail tile to view the image in full screen, it goes back to flat red with no logo.

Okay, some sort of curse is in play here.

Take a screenshot of the full-screen image. Do you see the logo flash?

Zoom in to the image. Do you see the logo appear, but only near the edges of the display?

Computers!

I'm not getting that - in Photos, looking at the full size flat-red version, and taking a screenshot, I don't see the logo flash at any time during that process. Nor on the edges when I resize.

Augh. Bizarre. Oh, do you have the "pop-up" overlay with icons for share, filters, etc. visible? (The one which appears when you tap the image.)

On my Pixel 3 XL, the behaviors I described occur, and also the logo is invisible unless the overlay is shown (in which case it's drawn only near the edges, unless you're taking a scree...oh.

I get it.

Image math is getting done internally in a wide gamut. Including alpha blending. But it's converted to sRGB before being displayed.

The things I described all, I suspect, modify the image- mostly by just dimming it, and the resulting dimmed wide color values map to different sRGB colors (where the undimmed colors all map to the same shade of red.)

I have a hunch that the internal management of the image by the application you've described is similar to the case of another comment where the logo could be seen in Windows after saving the file in MS Paint.

it's entirely possible that the preview compresses the color space in just the right way to show the separation. reducing colors can shrink image sizes quite a lot.

as to what's actually happening: not a clue! just pointing out possibilities :)

worked on my pixel 2 by setting the chrome flag to force the profile

Copying the image into Microsoft Paint shows the logo too.

If anyone is curious: https://i.imgur.com/IGTAWZF.png

Why is it that you can see it if you screenshot it?

The steps I took were: Right click on the image and selected copy. Paste it into Paint (which showed the logo).

I then saved it as a PNG (still showing the logo in Windows image viewer) and uploaded to Imgur. I assume pasting it into paint compressed the colors?

I saved it as a PNG and uploaded it. I don't know the technical details behind this but I'm assuming Paint compressed the colors.

PNGs are saved as sRGB by default, and so the differences aren't remapped away by the OS like they would be if the PNG was saved with a wider color space.

wait so if you screenshotted that.. what ends up saved in the PNG? Does the image clipboard now automatically have 2 versions of any screenshot; a wide colour version and some sort of normalised 8 bit version?

I'm looking at this from a macbook pro 2015 so I assume no wide colour support (?), yet I see the logo. Which conversion, at which step, caused that effect?

2015 MacBooks are not Display P3. What browser are you using, as that is incorrect behaviour.

The clipboard here is probably copying the image buffer in the untransformed state, and pasting it into MSPaint would dump those values incorrectly.

I see the same thing in both Firefox and Safari, on a non-P3 display: the original image is solid red, but the copied image shows the logo. So it looks like a conversion did actually happen at some point.

The transform to display the "solid red" block is actually the post-transformed data. The clipboard (rightfully) is carrying the original source buffer.

The issue would be the mechanics of the copy (attaching metadata) and pasting (interpreting the metadata in conjunction with the source image buffer.)

So technically, no, there's no conversion on the source data, it's the representation in the pasted context that's the issue.

My P30 Pro is listed as being wide color gamut capable : https://consumer.huawei.com/latin-en/phones/p30-pro/specs/

Yet I cannot get the android logo to display on Chrome or when the picture is downloaded and viewed on the default photo viewer.

Oh well maybe a future update will solve this issue. :p

Okay I just set the color mode from "vivid" to "normal" and now I can see the logo. Cool!

Fyi, never, ever use a monitor/TV in "vivid" setting. It sets the brightness, contrast and backlight settings to absurd values and clips a whole bunch of colors on the low and high luminance ranges resulting in a severely restricted dynamic range. A byproduct of this is that regular images appear super saturated and "vivid". Also, if you have an OLED or Plasma, vivid mode will almost certainly accelerate screen burn-in (I've even seen this happen on LCD TVs).

Thanks for the tip friend!

Actually I'm a hobby photographer, and I generally favor accurate color representation over any other special color modes. I do remember playing around with the settings when I got my phone and I think I just forgot to switch the color mode back to normal from vivid.

On my Mi 8 it works fine in Firefox, the default gallery app doesn't show it at all, and Google Photos shows it in the gallery view but not full screen. Oops...

If you are on a Mac, try changing your color profile in System Preferences | Displays | Color to something like 'Adobe RGB' or 'Display P3'. That allowed me to see the logo, as for a difference in the photos in the original post, not so much...

This test suggests that FF on Android doesn't properly work with color profiles: https://photographylife.com/is-your-browser-color-managed (the images are identical for me in FF on desktop, but not on the phone).

Which would mean that the red logo is just a result of mismapped colors.

I was pretty surprised to see the logo on a phone from 2011 with a rather meh screen…

Weird. I have a Pixel 3 XL, running Android P. I can see the Android logo in Firefox, but not in Chrome or Google Photos.

I tried setting the flag (chrome ://flags/#force-color-profile) and choosing P3, but I still see just a red square in Chrome.

EDIT: muro's tip (open in photos (menu -> device folders)) worked. Not sure why opening the same image from the Photos home screen doesn't work.

curiously enough, if I display this logo inside the firefox browser it is invisible (just a red square).

However, donwloading the png file and opening it on any image viewer it shows two different shades of red. I guess firefox is applying a silly color contrast change to its images before displaying them.

Just to add my own observations (Ubuntu Disco, FF 66) - it's also solid red for me in Firefox, but if I download it I can see the Android image in the preview in Gnome's file browser. If I open it up in Ubuntu / Gnome's "Image Viewer" application it's solid red, but works fine in Shotwell.

It's also solid red in GIMP 2.10, which surprised me.

On my Linux desktop, firefox, it's solid red. On my OnePlus 5T phone, it's solid red in Chrome, but an android logo in Firefox. Ah, if I download the file I see the logo with eom (eye of mate), though it's much less obvious than on the phone.

Moto G6+ with Firefox here, can clearly see the android logo. Not sure that this test is unequivocal.

It seems like others are having similar results. Some image libraries seem to be reducing the color space and changing the values. It could be an issue of P3 aware vs P3 capable. But I’m not entirely sure why it’s so hit or miss.

W10, on left ile is opened in IrfanView, right in latest Vivaldi: https://i.imgur.com/s8O5arl.jpg

On my Surface Go, it's solid red in Chrome and (surprisingly) Affinity Photo, but not Paint. I'm surprised that Paint has better support for this than a paid photo editing app.

I can't see any logo on a pixel 3 xl in chrome.

Edit: answered below - download to device, open in photos (menu -> device folders)

2015 MBP, Chrome/Safari will show a completely red image, copying it over to iMessage gives the red Android logo.

There is a bug there. You should be seeing a completely red image. Somewhere in your copy/paste step either (a) the color profile is being stripped out, or (b) the software you use to view the image is not properly respecting the color profile.

I believe both A and B are at work; it's probably a direct copy of the input buffer without metadata making B likely impossible, if it were trying at all, which I'll speculate isn't even a possibility.

Copying an image from one application to another should not strip image metadata. If it does that is a bug.

I’m not sure that clipboard implementations provide ancillary metadata? Nor would it be interpreted given the wild-west application development model where application developers are the folks who would need to implement support?

It is definitely possible to copy/paste images on the Mac while preserving image metadata. That behavior should be the default. If this is broken when copying between two Apple-provided applications then that is definitely a bug.

Good tip about FF, on my Pixel 2 Chrome shows just the plain red square, while FF reveals the Android logo.

Interestingly, on an OSX laptop, Chrome does not display it on one monitor but does on the other. Firefox displays it on both.

tl;dr: (╯°□°）╯︵ ┻━┻ color is hard.

I am glad to see my desktop machine isn't being left behind with this. In stock LTS Ubuntu the default image viewer shows the Display P3 images as does Firefox. The thumbnail in the file browser also has the logo showing.

Not sure about Chrome as I set the color flags to be sRGB a long time ago as, compared to Firefox, colours in Chrome are unsatisfactory on Linux.

I also tried on a consumer grade laptop that runs the latest (19.04) Ubuntu with one of those glossy screens, definitely not designed for Display P3. This failed in Firefox, Chrome, Gimp but the thumbnail in the file browser came good. How come when the hardware isn't there for it?

It seems like 25% of the colours are missing with a lot of that being green, green being quite an important colour. It must be possible to have some creative fun with this. If you can get images that only kids can see on their phones but adults not see on their boring PCs then you could have some variant of 'satanic backmasking' going on.

'Satanic backmasking' was where you could hear stuff about Satan on Beatles records if you played them backwards, listening whilst stoned. Politicians bothered themselves about young minds being corrupted by such things back in the day.

Maybe DCI-P3 images can court a similar controversy, shame April Fools Day is a lame day of corporate gags where nobody is fooled, otherwise DCI-P3 is ripe for moral panic, terrorising the adults with another thing for them to get their politicians frenzied about.

I hope Chrome gets to do colour a bit better, to Firefox standards. Otherwise we will be with half the world's screens not showing all the colours. Although not the same gap as between colour and monochrome, it is a huge difference to anyone that works with colour and needs subtle colour variations.