ColorManagement: Add Linear P3 transforms #25529
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Author
|
Holding off on this — not sure Linear P3 will be needed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related:
Terminology:
Note that "Linear Display P3" is not a thing — Display implies sRGB transfer functions, which a linear color space does not have. So the terms "display-p3" vs. "p3-linear" are intentional, and reflect W3C naming as well to my understanding.
This should be considered experimental — use of a wide-gamut working color space is going to take some deeper investigation, and we may decide that p3-linear is not necessary. But it is considerably easier to test than rec2020-linear or acescg, under current browser support.
/cc @WestLangley