1517539 - Image clipboard not retaining ICC profile

Status: RESOLVED DUPLICATE of bug 1431518

(Firefox :: Untriaged, defect)

Description

[butlergames]

Attachment: ICCProfileBugExamples.png

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:64.0) Gecko/20100101 Firefox/64.0

Steps to reproduce:

macOS Mojave 10.14.2 (18C54) running Firefox 64.0

Image editing software, like Photoshop, can read ICC profiles from the clipboard. If you copy an image and make a new document, the default New Document profile will match that of the copied image. This is a Firefox bug, but requires additional software to inspect; Photoshop or Affinity Photo (https://forum.affinity.serif.com/index.php?/topic/37508-icc-profile-of-a-copied-image/&).

Steps:
1. Start Firefox
2. Press Cmd+N to open a new browser window
3. Paste https://www.missionmedia.com/uploads/image/news/1080x1920_blog_post.jpg in the address bar and press Enter. (Any image URL with a color profile will work)
4. Ctrl+Click or right click the image and select Copy Image
5. Start Photoshop (or similar image editing software)
6. Press Cmd+N to create a new document from the clipboard data
7. Expand the Advanced information area




Actual results:

The color profile displayed under Advanced will show Generic RGB Profile and disregard the ICC profile of the copied image. This is all independent of how the image has been rendered within Firefox and independent of all gfx.color_management values in about:config. A forced ICC profile within Firefox will only change how the image is displayed in browser. Copied images will still lose this data when sent to the clipboard and always revert to Generic RGB Profile.


Expected results:

Copying an image from Firefox should send that image's ICC profile to the clipboard as well and retain that information. Images pasted into editing software need to keep this data in order to preserve color fidelity. This is the behavior in Chrome.

Comment 1

[Timea Cernea [:tbabos][inactive]]

Hi butlergames,

This issue seems to be the same as the one described in Bug 1431518, correct me if I'm wrong here.
Marking this as a duplicate for now.