Features/Jetpack/Add-onTab-API

Status

Team

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

`

Non-goals

`

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

`

Accessibility

`

Quality Assurance review

`

Operations review

`

Stage 4: Development

9. Implementation

`

Stage 5: Release

10. Landing criteria

`

Feature details

Team status notes