Confirmed users, Bureaucrats and Sysops emeriti
2,088
edits
mNo edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
|Feature stage=Draft | |Feature stage=Draft | ||
|Feature status=In progress | |Feature status=In progress | ||
|Feature version=Firefox | |Feature version=Firefox 15 | ||
|Feature health=OK | |Feature health=OK | ||
}} | }} | ||
| Line 39: | Line 39: | ||
|Feature implementation plan=Meta-bug: {{bug|731779}} | |Feature implementation plan=Meta-bug: {{bug|731779}} | ||
* Set up Git->HG syncing infrastructure (Non-blocking: If not ready by landing time, can do weekly drops.) | |||
* Work with browser/toolkit module owners to determine code location in each component. | |||
* Land CommonJS loader in Firefox (In toolkit, have Mossop to review.) | |||
* Jetpack housecleaning required before landing | |||
** Misc cleanup (removing window-utils, etc.) | |||
** Packagelessness | |||
** Separate core APIs into Browser and Toolkit sets | |||
* Land core APIs in Firefox | |||
Each of these Loader usage scenarios should be supported and documented with code samples: | |||
* Inclusion into XUL window scope | |||
* Inclusion into non-window scopes (JS XPCOM, JS Modules) | |||
* Support shared & private instances | |||
|Feature security review=The Add-on SDK has gone through multiple security reviews. Should schedule another one to review how/where the code lives and is initiated/loaded inside Firefox. | |Feature security review=The Add-on SDK has gone through multiple security reviews. Should schedule another one to review how/where the code lives and is initiated/loaded inside Firefox. | ||
}} | }} | ||