Color management for a pic only with EXIF InteropIndex
Categories
(Core :: Graphics: Color Management, enhancement, P3)
Tracking
()
People
(Reporter: bxp04335, Unassigned)
Details
(Whiteboard: [gfx-noted])
Attachments
(2 files)
Reporter | ||
Comment 1•8 years ago
|
||
Updated•8 years ago
|
Updated•2 years ago
|
Comment 2•2 years ago
|
||
Firefox is treating the example image without embedded ICC profile as untagged.
It then correctly assumes it to be sRGB (W3C standard https://www.w3.org/TR/css-color-4/#untagged).
Embedding an ICC profile is one -widely recognised- way to tag an image.
However as W3 put it "Image formats may also use other, equivalent methods, often for brevity."
The interoperability index , used by most if not all camera manufacturers, is one of those methods used for brevity.
It's part of DCF - Design rule for camera filesystem specification.
Most straight out of camera JPEG images will not have an embedded ICC profile, but the EXIF metadata does contain the "InteropIndex" tag.
It's even the very first tag 0x0001 (https://www.exiftool.org/TagNames/EXIF.html) and part of the official EXIF specification.
It would be a nice addition if Firefox could read this EXIF tag and treat an image accordingly (as tagged) instead of falling back to sRGB (as if untagged).
Comment 3•2 years ago
|
||
(In reply to [:Propheticus] from comment #2)
Firefox is treating the example image without embedded ICC profile as untagged.
It then correctly assumes it to be sRGB (W3C standard https://www.w3.org/TR/css-color-4/#untagged).
...
I just realised (and tested) this is only true because I have 'gfx.color_management.mode' set to '1' (always colour manage) instead of the default '2' (only colour manage when image is tagged).
So it's even worse. With default settings, Firefox is not W3C compliant.
Description
•