From MozillaWiki
Jump to: navigation, search
Please use "Edit with form" above to edit this page.


Add-On Tab API
Stage Planning
Status In progress
Release target Add-on SDK 1.5
Health OK
Status note `


Product manager David Mason
Directly Responsible Individual `
Lead engineer `
Security lead Dan Veditz
Privacy lead `
Localization lead `
Accessibility lead `
QA lead `
UX lead `
Product marketing lead `
Operations lead `
Additional members `

Open issues/risks


Stage 1: Definition

1. Feature overview

This API should give add-on developers the opportunity to have their add-on create a new tab with a reduced-chrome view and the ability to add html content to the tab.

2. Users & use cases

The best example of an add-on tab is the about:addons page. This page, when launched will take away the chrome for the awesomebar/search as well as a visible bookmarks bar leaving the user with a special page where the content is the most important element. This can be useful for preferences and special content.

3. Dependencies


4. Requirements




Stage 2: Design

5. Functional specification


6. User experience design


Stage 3: Planning

7. Implementation plan

The implementation of this API should be fairly straight-forward as the page content implementation should be similar, if not the same, as the content allowed in currently in a panel. Therefore, new implementation should just be the creation of a new tab, and the creation of the reduced-chrome interface for that tab.

8. Reviews

Security review


Privacy review


Localization review




Quality Assurance review


Operations review


Stage 4: Development

9. Implementation


Stage 5: Release

10. Landing criteria


Feature details

Priority P1
Rank 999
Theme / Goal `
Roadmap `
Secondary roadmap `
Feature list `
Project `
Engineering team `

Team status notes

  status notes
Products ` `
Engineering ` `
Security sec-review-needed bug 744913
Privacy ` `
Localization ` `
Accessibility ` `
Quality assurance ` `
User experience ` `
Product marketing ` `
Operations ` `