Features/Jetpack/Add-onTab-API

From MozillaWiki
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
Please use "Edit with form" above to edit this page.

Status

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

{{#set:Feature name=Add-On Tab API

|Feature stage=Planning |Feature status=In progress |Feature version=Add-on SDK 1.5 |Feature health=OK |Feature status note=` }}

Team

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 `

{{#set:Feature product manager=David Mason

|Feature feature manager=` |Feature lead engineer=` |Feature security lead=Dan Veditz |Feature privacy lead=` |Feature localization lead=` |Feature accessibility lead=` |Feature qa lead=` |Feature ux lead=` |Feature product marketing lead=` |Feature operations lead=` |Feature 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

`

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

` {{#set:Feature open issues and risks=` |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. |Feature users and 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. |Feature dependencies=` |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature 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. |Feature security review=` |Feature privacy review=` |Feature localization review=` |Feature accessibility review=` |Feature qa review=` |Feature operations review=` |Feature implementation notes=` |Feature landing criteria=` }}

Feature details

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

{{#set:Feature priority=P1

|Feature rank=999 |Feature theme=` |Feature roadmap=` |Feature secondary roadmap=` |Feature list=` |Feature project=` |Feature 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 ` `

{{#set:Feature products status=`

|Feature products notes=` |Feature engineering status=` |Feature engineering notes=` |Feature security status=sec-review-needed |Feature security health=Blocked |Feature security notes=bug 744913 |Feature privacy status=` |Feature privacy notes=` |Feature localization status=` |Feature localization notes=` |Feature accessibility status=` |Feature accessibility notes=` |Feature qa status=` |Feature qa notes=` |Feature ux status=` |Feature ux notes=` |Feature product marketing status=` |Feature product marketing notes=` |Feature operations status=` |Feature operations notes=` }}