[svgwg] Make us of HTML "read-back-allowed" rendering for SVG-as-image (#1151)

schenney-chromium has just created a new issue for https://github.com/w3c/svgwg:

== Make us of HTML "read-back-allowed" rendering for SVG-as-image ==
As part of the [HTML-in-Canvas](https://github.com/WICG/html-in-canvas) effort, the concept of `read-back-allowed` rendering is being added to the HTML spec. See https://github.com/whatwg/html/pull/12554

`read-back-allowed` rendering is a mode whereby any privacy sensitive content in the DOM is ignored for painting. It is used by HTML-in-Canvas to enable DOM content in `canvas`, WebGL and WebGPU textures where the content must be privacy preserving by default.

We are interested in referring to this rendering mode in the SVG [Processing Modes](https://www.w3.org/TR/SVG2/conform.html#processing-modes) spec section for foreign object content rendered in "Secure" modes. Doing so would make it possible to never taint the HTML canvas when SVG content is rendered into the canvas as an image. Currently browsers taint the canvas when SVG content with foreign object is included in some circumstances but not others, which is confusing for developers and bad for user privacy.

Please view or discuss this issue at https://github.com/w3c/svgwg/issues/1151 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 22 July 2026 14:59:20 UTC