CMYK profile images do not render in Microsoft Edge/IE/Windows Photos

[lxxiii]

A large JPG uploaded via Media in WPAdmin is processed into various sizes. The original renders in Windows 10 Pro Edge/IE/Photos. The processed images do not render. Processed images do render in Chrome and Firefox. Converting the large JPG to PNG using Photoshop and uploading results in processed images that do render in Edge/IE/Photos.

This independent from Ticket 36534, the Imagick thread issue, which I also encountered on my Web hosting virtual private server. The .htaccess thread count line fixed my HTTP Error image upload issue. 4.5.2 is slated to contain that fix.

I first noticed this non-rendering issue in 4.5; no change with 4.5.1. I was on 4.5 before I ever encountered the image in question.

This non-rendering image has been discussed with a developer on the Edge team. It has been formally submitted to Windows Feedback, too. Is it specific to this one file? Is it an Edge/IE issue? I can't tell. Other processed JPGs do render in Edge/IE/Photos.

Original uploaded through Media still renders in Edge:
​https://zulu.international/media/WRN_Ambassador_logo.jpg

Processed 300x228 does not render in Edge:
​https://zulu.international/media/WRN_Ambassador_logo-300x228.jpg

Downloading the 300x228 and opening it in Windows Photos does not work, either.

Original file has been attached for reference.

(The source JPG image is from NOAA, and contains a trademarked image; it is used with permission on my site. I do conceded that it may be an image conflict, and not necessarily a bug in WordPress. However, it is WordPress processing that creates the non-rendering image.)

With WP 4.5, it was announced that image processing was enhanced, so it leads me to believe something with this JPG file is incompatible with the changes. I simply cannot determine if it's just this one file, or a symptom of a larger problem.

For comparison, here is an original JPG I created in Photoshop, uploaded via Media, which renders in Edge:
​https://zulu.international/media/arrl-wx0zzz.jpg

This is the WordPress processed 300x300, which also DOES render in Edge:
​https://zulu.international/media/arrl-wx0zzz-300x300.jpg

Better safe than sorry to expose a potential bug and have this ticket closed, than to let it go unnoticed.

[lxxiii]

Original source of WRN_Ambassador_logo.jpg (Image Trademarked by NOAA! Used with permission.)

[lxxiii]

HEY! I have a WordPress 4.4.2 install that I just uploaded this large JPG to. It uploads and is processed.

The 300x228 processed image from 4.4.2 DOES render in Edge:
​http://www.climategen.org/wp-content/uploads/WRN_Ambassador_logo-300x228.jpg

[lxxiii]

Some newly discovered info:

The original JPG is CMYK. 1.16MB. 3019x2294.

The 4.4.2 processed JPG is RGB. This 300x228 JPG is 17KB.

The 4.5 processed JPG is CMYK. This 300x228 JPG is 588KB!

Is 4.5 now retaining CMYK for a reason? Does Edge not support CMYK JPGs? Just some thoughts and perspective...

[zuluintl]

Hi. I legally changed my business name. lxxiii is now zuluintl; I'll be monitoring and responding to any inquiries from this account now. Thanks for reviewing.

[desrosj]

#40488 was marked as a duplicate.

[desrosj]

Seems this one lost a milestone somewhere along the way.

I've done some testing, and it seems that generated image sizes are maintaining a CMYK color model. I do recall encountering this myself at some point along the road in the past, and changing the image to RGB fixed the issue.

I can't seem to find any official documentation of a problem with CMYK in IE/Edge, but in my testing so far, it seems that CMYK model images no longer have issues in Microsoft Edge (all versions of IE are no longer supported by WordPress). I tested on Windows 10, and was able to go back and test Edge 18 (which is pretty old) and Edge 80-99 (more modern versions), and all of these successfully rendered CMYK model images.

Because nothing is technically broken now, I almost lean towards closing this as a wontfix.

Reviewing the Slack conversations linked above, it did seem that there was general agreement that images generated for use on screen should have an RGB model (which I do agree with). My hunch is that there would be a difference in file size between RGB and CMYK images, but that's not based on any actual data.

I'm also not familiar with how color profiles work in WebP format images. With #55443 aiming to make WebP the default image format, It's worth exploring. @adamsilverstein do you have any insight here?

I'm adding the close suggestion pending a 2nd-opinion.

[desrosj]

#47840 is a potential duplicate here. And if not, it may add weight to the suggestion to enforce RGB above.

[adamsilverstein]

I'm also not familiar with how color profiles work in WebP format images. With #55443 aiming to make WebP the default image format, It's worth exploring. @adamsilverstein do you have any insight here?

Color profiles are generally well supported in WebP as far as I know. I am happy to generate some WebPs (with GD and Imagick) from the sample image and run some cross browser testing on them to check though.

[adamsilverstein]

Reviewing this I think we can go ahead and close. We can re-open if this issue resurfaces, it might be highly dependent on the underlying image engine processing the images.