1853414 - Consider moving Glean bindings to `dom/chrome-webidl` from `dom/webidl`

Status: NEW

(Toolkit :: Telemetry, task, P3)

Description

[Chris H-C :chutten]

dom/webidl is different from dom/chrome-webidl in that changes to the latter do not require a DOM Peer to review (bug 1442931). These should only be limited to APIs that are never exposed to web content, which I imagine we wouldn't mind limiting Glean to.

It requires:

• Determining if this is something Glean wants. Maybe we do want DOM Peers to review our changes? Maybe we do want to expose some Glean APIs to certain web content?
• Changing DOM webidl codegen to broaden its idea of what Funcs are permitted.
• MOST IMPORTANTLY: chatting with DOM Peers on #dom:mozilla.org to see if this is cool.

Something to consider.

Comment 1

[Nick Alexander :nalexander [he/him]]

(In reply to Chris H-C :chutten from comment #0)

dom/webidl is different from dom/chrome-webidl in that changes to the latter do not require a DOM Peer to review (bug 1442931). These should only be limited to APIs that are never exposed to web content, which I imagine we wouldn't mind limiting Glean to.

It requires:

• Determining if this is something Glean wants. Maybe we do want DOM Peers to review our changes? Maybe we do want to expose some Glean APIs to certain web content?

I can't imagine we would ever do this. The only situation I can envision is to expose Glean to first-party content (accounts.firefox.com or similar), and we have mechanisms for doing so (postMessage to chrome contexts) that don't change anything about the content context.

Comment 2

[Chris H-C :chutten]

Attachment: WIP: Bug 1853414 - Move Glean webidls back to chrome-webidl/ r?nika!