Features/Jetpack/Jetpack-Chrome-mods

Status

Team

Open issues/risks

`

Stage 1: Definition

1. Feature overview

Firefox has always presented itself to developers as a browser that allows customization. While this can often be painful from the point of view of user experience, it also provides great power in extensibility and innovation. Jetpack has always embraced the idea of modification and extension but only for shallow integrators where we felt some responsibility to help direct better user experience guidelines through offering only elements that would lend themseleves to that better experience. While that does a great deal to help keep the experience clean, it also frustrates those who want to integrate more deeply into the browser. With a new focus on Deep Integrators we want to investigate what kinds of modifications we can allow SDK developers to make to the desktop UI.

Chrome mods should allow the developer to easily alter Firefox chrome, possibly in a manner that is very similar to page-mods with the exception that the chrome being altered must first be properly identified before the developer can alter that element.

The first phase of the work will be to identify what sorts of modifications developers want and that could be made safely.

The second phase should be to develop an API for making those changes.

Subsequent phases will involve implementation dependent on the previous phases.

2. Users & use cases

It is part of the initial work to identify what the users and use cases are here.

3. Dependencies

`

4. Requirements

`

Non-goals

`

Stage 2: Design

5. Functional specification

`

6. User experience design

`

Stage 3: Planning

7. Implementation plan

`

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