This spec was originally developed in the W3C's ColorWeb community group along with the 2D canvas color management proposal at
https://github.com/WICG/canvas-color-space/blob/main/CanvasColorSpaceProposal.md
Implementation of WebGL color management API WebGL allows specification of - the color space that its drawing buffer is - the color space that content should be converted to when importing as a texture This feature is to update our implementation to include this functionality. Prior to this feature, both of these defaulted to sRGB. Now they can also use "display-p3".
This allows a WebGL canvas to specify its color space. This functionality is already present for 2D canvas, images, and video content.
Debugging is currently limited to sRGB colors. This limits visibility into wide color gamut image, video, and 2D canvas. This limitation is being looked at in the context of adding CSS color level 4 support.
No milestones specified
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGnfxj_6radHqyNz4Sxa3SxZET-93xJCdMdZe6WptHxOLyhC3A%40mail.gmail.com.
Web developers: Strongly positive
Other signals:Privacy: N/A
This exposes no information about the user's system to the web. This API can be used on systems that do not support wide color gamut (the out-of-gamut colors are clipped, as they are for 2D canvas, images, and video).Security: N/A
This allows a WebGL canvas to specify its color space. This functionality is already present for 2D canvas, images, and video content.
Debuggability
Debugging is currently limited to sRGB colors. This limits visibility into wide color gamut image, video, and 2D canvas. This limitation is being looked at in the context of adding CSS color level 4 support.
Is this feature fully tested by web-platform-tests?
No, this is tested instead by WebGL conformance tests.
----Flag name
WebGLColorManagementRequires code in //chrome?
NoTracking bug
https://crbug.com/1208480Sample links
https://ccameron-chromium.github.io/webgl-examples/p3.htmlEstimated milestones
No milestones specified
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/4814886323355648
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAGnfxj_6radHqyNz4Sxa3SxZET-93xJCdMdZe6WptHxOLyhC3A%40mail.gmail.com.
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMYvS2ekSB4fFQ0-NHHs2ESFPu5jHauTEZWiURVGSWcbDcF0VQ%40mail.gmail.com.
Web developers: Strongly positive
Other signals:Privacy: N/A
This exposes no information about the user's system to the web. This API can be used on systems that do not support wide color gamut (the out-of-gamut colors are clipped, as they are for 2D canvas, images, and video).Security: N/A
This allows a WebGL canvas to specify its color space. This functionality is already present for 2D canvas, images, and video content.
Debuggability
Debugging is currently limited to sRGB colors. This limits visibility into wide color gamut image, video, and 2D canvas. This limitation is being looked at in the context of adding CSS color level 4 support.
Is this feature fully tested by web-platform-tests?
No, this is tested instead by WebGL conformance tests.Can you link to the specific tests? This is really intended to ask about automated conformance testing generally, sorry for my ignorance of how the WebGL conformance tests work.
On Tue, May 17, 2022 at 3:40 PM 'Christopher Cameron' via blink-dev <blin...@chromium.org> wrote:
TAG review status
N/A. Canvas 2D color managment API already TAG reviewed at
This specification change was developed in Khronos and followed the processes there.Risks
Interoperability and Compatibility
Gecko: Positive Developed in close collaboration with Mozilla, spec changes reviewed by Mozilla.
WebKit: Positive Discussed in ColorWeb CG with WebKit representatives
Web developers: Strongly positive
Web developers: Strongly positiveCould you give examples of developer support?
Web developers: Strongly positiveCould you give examples of developer support?Not to speak for Chris Cameron, but this support was requested, with urgency, by Adobe.-Ken
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMYvS2dk0%2B1MM8pG6kfLEVQSx_yNEoh6-cF80mmOuv_JenxQeA%40mail.gmail.com.
On Wed, May 18, 2022 at 4:04 PM Ken Russell <k...@chromium.org> wrote:On Wed, May 18, 2022 at 3:40 PM Chris Harrelson <chri...@chromium.org> wrote:Hi, comments below.On Wed, May 18, 2022 at 11:48 AM Ken Russell <k...@chromium.org> wrote:On Tue, May 17, 2022 at 3:40 PM 'Christopher Cameron' via blink-dev <blin...@chromium.org> wrote:
TAG review status
N/A. Canvas 2D color managment API already TAG reviewed atShould this intent reuse issue 646 then? Are the considerations and API almost exactly the same as in 2D canvas? Another option is to comment on that issue describing the WebGL variant of the same feature, and calling out the notable differences the TAG needs to be aware of to provide useful feedback.This specification change was developed in Khronos and followed the processes there.Risks
Interoperability and Compatibility
Gecko: Positive Developed in close collaboration with Mozilla, spec changes reviewed by Mozilla.
WebKit: Positive Discussed in ColorWeb CG with WebKit representativesPlease file for official signals. Participating in discussions is not the same as officially supporting.I'd like to respectfully point out that this API was agreed upon by all major browser implementers in Khronos' WebGL working group, whose processes have been well established over the last decade. The WebGL working group owns the responsibility for evolving this portion of this web API, and the requirement in Blink's processes to fetch signals is causing duplicate work to be done in this context.I would like to respectfully request that Blink's processes be changed to not require implementation signals for WebGL specification changes. Any such changes are already only made with full agreement among Gecko, WebKit and Blink engineers.Got it, ok. We already have an exception in two cases, let's work together on adding it to bit.ly/blink-intents.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+unsubscribe@chromium.org.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/dc570756-2c4d-49f0-8a4a-05b11fd235e3n%40chromium.org.