Philip Jägenstedt
Philip Jägenstedt
The model in https://github.com/w3c/trusted-types/pull/597 was that Trusted Types would ensure that a policy-controlled and unforgeable `TransformStream` sits in front of the parser. But that's a bit rigid and I'm not...
> > But that's a bit rigid and I'm not sure what it would take to make it unforgeable. > > We can't have a subclass or annotate it with...
> But I guess it could be odd having different API shape for trusted vs not trusted usages. @lukewarlow yes, the extra argument when using a TT policy made it...
@noamr good ideas! > Another option is to override the pipe operation of the trusted readable stream I suspect that we'd have to add steps to https://streams.spec.whatwg.org/#readable-stream-pipe-to which would be...
> use a stream that passes unforgeable chunks, and as long as they are in order they don't need to go through the default policy's stream This option seems the...
The root cause of this is probably the same as https://github.com/bubkoo/html-to-image/issues/542, a lot of custom properties, which are included in `getComputedStyle()` and getting copied for many elements. I'll comment there...
The input was https://w3c.github.io/speech-api/index.html
If https://chromestatus.com/data/blink/webfeatureprops would also use "view-transitions", then that would also serve as a manifest of all features that have a use counter in Chromium. That currently requires parsing enums.xml.
cc @captainbrosset
I just noticed this too. This isn't useful to see in blink-dev emails.