CMYK images are rendered with inverted colors

[ioweb-gr]

Preconditions (*)

1. Magento 2.3.1
2. ImageMagick as image processor
3. One CMYK image

Steps to reproduce (*)

1. Install Magento 2.3.1 and use ImageMagick as image processor.
2. Create a product and upload an image in CMYK color profile.
3. The image displays properly in backend in product edit page because it shows the original image.
4. Check the product in frontend and notice that the image is resized via ImageMagick but the colors are inverted.

Expected result (*)

1. The image displays properly would be ideal but at least the user should be warned that the image is saved in a color space that Magento 2 cannot handle so it will not be be converted correctly.

Actual result (*)

1. Image is resized but the colors are inverted.
   

Unfortunately the users of an eshop are not usually proficient in the handling of apps like photoshop and they will probably upload lots of images they downloaded from the web or from their providers. Thus it's very possible that they will encounter situations like this.

I think the system should at least warn them that it cannot process the image correctly if it can't handle the conversion.
Perhaps Imagick::transformImageColorspace could be used to handle it silently?

Here's a sample image

[m2-assistant]

Hi @ioweb-gr. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento-engcom-team give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@ioweb-gr do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

[ioweb-gr]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @ioweb-gr. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @ioweb-gr, here is your Magento instance.
Admin access: https://i-22375-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[ioweb-gr]

Reproduced on Magento 2.3-develop instance

[m2-assistant]

Hi @dmytro-ch. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento-engcom-team give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento-engcom-team give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[dmytro-ch]

@magento-engcom-team give me 2.3-develop instance

[magento-engcom-team]

Hi @dmytro-ch. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @dmytro-ch, here is your Magento instance.
Admin access: https://i-22375-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.