Philip Jägenstedt

@Kaiido thank you for the review! I've fleshed things out more, renaming to `drawHTMLElement()` (because `drawElement()` will probably not be workable in WebGL) and adding the `layoutsubtree` attribute. There's still...

I've fleshed this out some more now, in particular the hit testing.

Thanks for the review @progers! I've left two comments unresolved where I'd like more feedback.

Oh... I merged https://github.com/w3c/webref/pull/1736 but https://github.com/w3c/webref/actions/runs/20142389583 failed. When this is merged, how can we make that release happen?

For anyone who has the ability to patch their copy of html2canvas for a quickfix, the change in https://github.com/niklasvh/html2canvas/pull/3252 should do the trick. Note that the change was reverted in...

This change is rolling out again in Chrome 141, tracked by https://chromestatus.com/feature/5070655645155328. The workaround for anyone affected is to apply https://github.com/niklasvh/html2canvas/pull/3252 to switch to another library.

I'm trying to make the API surface concrete enough to start writing spec text. The starting point in the [explainer](https://github.com/WICG/declarative-partial-updates/blob/main/patching-explainer.md) is a `patchUnsafe()` method that returns a `WritableStream`. Fitting TT...

> The way I see it, the TT step should be a `TransformStream` (with a new `createHTMLStream` method or so if exists), and its `writable` part would be what's returned...

I've never used Trusted Types, so let me double check my understanding. The most straightforward and typical way to use TT is a header like `Content-Security-Policy: require-trusted-types-for 'script'; trusted-types my-policy`...

In https://github.com/w3c/trusted-types/pull/597 I have sketched out some idea of what the TT spec changes might look like.