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
I'm requesting a TAG review of 2D canvas floating point!
The output bitmap of a CanvasRenderingContext2D (or offscreen) defaults to being 8-bit on all browses (although it is not specified this way). This change makes that behavior explicitly specified, and add the option, via CanvasRenderingContext2DSettings, to specify that it can be 16-bit floating point.
The comments for the larger TAG review that are relevant for this the ones relating to toDataURL and toBlob, which have been clarified (both in terms of immediate behavior and future extensions in HDR work) in the smaller explainer.
I'm requesting a TAG review of 2D canvas floating point!
The output bitmap of a CanvasRenderingContext2D (or offscreen) defaults to being 8-bit on all browses (although it is not specified this way). This change makes that behavior explicitly specified, and add the option, via CanvasRenderingContext2DSettings, to specify that it can be 16-bit floating point.
Further details:
You should also know that...
A superset of this functionality was reviewed by TAG as part of the proposal for Adding support for High Dynamic Range (HDR) imagery to HTML Canvas. That proposal is being split into several independent components to be added individually.
The text was updated successfully, but these errors were encountered: