The graphics API this build was compiled against, or null when it was
compiled without GPU support. Names the API even where renderer is
"CPU", since the fallback happened inside that API.
The adapter as the driver names it -- "Discrete GPU (…)" -- or, on the
CPU, a phrase saying which reason put it there: manually disabled, the
pixel format needing it, a failed initialization, or a build without GPU
support.
OptionaldriverDriver name and version, where the API reports them. Vulkan does; Metal
omits the field on the GPU, and every CPU path reports the string
"N/A".
OptionalerrorWhy the GPU was not used, when that is a failure rather than a choice.
Absent on a working GPU, and null on a build compiled without support.
Which backend took this canvas -- not what the machine has. A canvas
built with gpu: false, and a float canvas that no GPU can composite,
both report "CPU" on a machine with a working GPU.
The canvas's own CanvasOptions.textContrast.
The canvas's own CanvasOptions.textGamma.
Threads in the rasterizing pool.
What one canvas is actually rendering on, as reported by Canvas.engine.
🧪 Not in the HTML Canvas standard.