Open
Bug 1748692
Opened 2 years ago
Updated 2 years ago
Move all Extension APIs webidl files into a separate webidl dir
Categories
(WebExtensions :: General, task, P3)
WebExtensions
General
Tracking
(Not tracked)
NEW
People
(Reporter: rpl, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [addons-jira])
All the webidl files related to the "Extension APIs webidl bindings" are currently part of the dom/webidl directory.
These webidl definitions are not meant to be exposed to the web content, and so every one of this webidl definitions should be made only visible in Extension globals (currently only in the background service worker, but they are meant to be exposed to Extension windows and Extensions content scripts sandbox in the future).
Currently the correct visibility is ensured by the explicit review and sign-off from a WebIDL peer that is required to land any change to webidl files listed in dom/webidl.
In the long run, we would like to:
- move all "Extension APIs webidl bindings" into a separate webidl directory (like the chrome-only webidl files are all in dom/chrome-webidl), e.g. dom/extensions-webidl
- have the expected "visibility" double-checked automatically at build time (as part of the existing automated processing of the webidl files)
- require a mandatory review from a "WebExtensions" module peer for landing changes to files in that separate webidl directory (e.g. dom/extensions-webidl)
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•