You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Among the steps in createImageBitmap is the following:
If image is an img element or a Blob object, let val be the value of the colorSpaceConversion member of options, and then run these substeps:
If val is "default", the color space conversion behavior is implementation-specific, and should be chosen according to the default color space that the implementation uses for drawing images onto the canvas.
If val is "none", output must be decoded without performing any color space conversions. This means that the image decoding algorithm must ignore color profile metadata embedded in the source data as well as the display device color profile.
At the time of writing of the spec, the only non-sRGB content on the web were images. As a consequence, the spec leaves as ambiguous how the color spaces of all other sources (e.g, videos, canvases, ImageData, etc) should be handled.
(See this comment for a more thorough discussion -- there is also a "don't imply that YUV to RGB conversion would be skipped" aspect).
The proposal in this issue is to remove the "If image is an img element or a Blob object" clause from the text (see this proposed commit), so that we remove this ambiguity in a way that treats all content the same.
Further clarifications of the behavior of createImageBitmap with colorSpaceConversion:"none" are needed, but I've separated out those issues into #10578.
The text was updated successfully, but these errors were encountered:
What is the issue with the HTML Standard?
Among the steps in
createImageBitmap
is the following:At the time of writing of the spec, the only non-sRGB content on the web were images. As a consequence, the spec leaves as ambiguous how the color spaces of all other sources (e.g, videos, canvases, ImageData, etc) should be handled.
(See this comment for a more thorough discussion -- there is also a "don't imply that YUV to RGB conversion would be skipped" aspect).
The proposal in this issue is to remove the "If image is an img element or a Blob object" clause from the text (see this proposed commit), so that we remove this ambiguity in a way that treats all content the same.
Further clarifications of the behavior of
createImageBitmap
withcolorSpaceConversion:"none"
are needed, but I've separated out those issues into #10578.The text was updated successfully, but these errors were encountered: