Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Coding Independent Code Points (CICP) and PNG cICP #922

Open
svgeesus opened this issue Nov 8, 2023 · 4 comments
Open

Coding Independent Code Points (CICP) and PNG cICP #922

svgeesus opened this issue Nov 8, 2023 · 4 comments

Comments

@svgeesus
Copy link

svgeesus commented Nov 8, 2023

Request for Mozilla Position on an Emerging Web Specification

Other information

CICP is a way to identify the color space and transfer function; specified in ITU-T-H.273 originally for video formats, it is now widely deployed and starting to be used in image formats such as AVIF and JPEG-XL. It is particularly used for HDR content, but can also be used for SDR content. Compared to an embedded ICC profile, which can be 10-20k for an RGB colorspace, it only adds 4 bytes of data because it is an enumeration.

For example, an image in BT.2100 color space with the PQ transfer function would signal this with the following four bytes:

9 16 0 1

while an image in Display P3 would use

12 13 0 1

Gecko already supports CICP in AVIF, see https://bugzilla.mozilla.org/show_bug.cgi?id=1634741

The need for PNG to support HDR images was identified at the W3C Color Workshop and incubated in the Color on the Web CG

PNG Third Edition adds the cICP chunk for CICP, and this is already supported in Chrome. It is produced by image editing applications including darktable and Adobe Photoshop.

@svgeesus
Copy link
Author

svgeesus commented Jan 9, 2024

WPT test results for cICP in PNG shows passes in Chrome and in Edge. Safari is shown as failing, because it relies on macOS support and the version of macOS used on WPT is too old. It passes in local testing on macOS Sonoma.

Thus, the only browser now failing is Firefox.

@svgeesus
Copy link
Author

svgeesus commented Feb 6, 2024

@tnikkel @emilio who in Mozilla should we be talking to about this?

@emilio
Copy link
Collaborator

emilio commented Feb 6, 2024

@tnikkel is a good guess. @jrmuizel and @kdashg might have opinions too?

@jrmuizel
Copy link

jrmuizel commented Feb 6, 2024

I don't see any reason not to support this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Unscreened
Development

No branches or pull requests

3 participants