Upstream IDL changes from Trusted Types

[lukewarlow]

• At least two implementers are interested (and none opposed):
  • Chromium
  • Gecko
• Tests are written and can be reviewed and commented upon at:
  • https://wpt.live/trusted-types/
• Implementation bugs are filed:
  • Chromium: Shipped
  • Gecko: https://bugzilla.mozilla.org/show_bug.cgi?id=1508286
  • WebKit: https://bugs.webkit.org/show_bug.cgi?id=266630
  • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): Not sure it's relevant to Deno?
  • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): …
• MDN issue is filed: Not applicable? Trusted Types as an API is already documented with examples of sinks.
• The top of this comment includes a clear commit message to use.

(See WHATWG Working Mode: Changes for more details.)

---

/dom.html ( diff )
/dynamic-markup-insertion.html ( diff )
/iframe-embed-object.html ( diff )
/infrastructure.html ( diff )
/references.html ( diff )
/workers.html ( diff )

[lukewarlow]

Sections to upstream:

• https://w3c.github.io/trusted-types/dist/spec/#extensions-to-the-windoworworkerglobalscope-interface - Not upstreaming as I don't think it's the norm to.

• https://w3c.github.io/trusted-types/dist/spec/#enforcement-in-document-interface

• https://w3c.github.io/trusted-types/dist/spec/#enforcement-in-domparser-interface

• https://w3c.github.io/trusted-types/dist/spec/#enforcement-in-element-shadowroot-interfaces

• https://w3c.github.io/trusted-types/dist/spec/#html-workers

• [-] https://w3c.github.io/trusted-types/dist/spec/#enforcement-in-sinks - Only HTMLIframeElement srcdoc upstreamed

• https://w3c.github.io/trusted-types/dist/spec/#enforcement-in-scripts - Still WIP so not upstreaming yet

• https://w3c.github.io/trusted-types/dist/spec/#enforcement-in-timer-functions - Still WIP so not upstreaming yet

• https://w3c.github.io/trusted-types/dist/spec/#enforcement-in-event-handler-content-attributes - Still WIP so not upstreaming yet

• https://w3c.github.io/trusted-types/dist/spec/#html-validate-the-string-in-context - Will be upstreamed as a separate PR

[annevk]

Inside an IDL block we use <span> to reference code constructs, not <code>. Looks mostly good otherwise.

[annevk]

@dontcallmedom do you foresee this causing any issues for the various IDL tools?

[dontcallmedom]

@dontcallmedom do you foresee this causing any issues for the various IDL tools?

none that I can see

[annevk]

I'll leave it to @domenic and @zcorpan whether they're okay with doing this incrementally.

[zcorpan]

I think incremental upstreaming is OK.

Are the open threads above resolved?

[lukewarlow]

Are the open threads above resolved?

Yeah apologies forgot to close them.

[lukewarlow]

is there a preference for what the commit message should say? And is there anything else that I need to do?

[zcorpan]

Upstream IDL changes from Trusted Types

Part of https://github.com/w3c/trusted-types/issues/476

and maybe repost #10199 (comment) there, since it's the tracking issue for upstreaming.

[lukewarlow]

Have changed the commit message and reposted that comment