Features/Jetpack/Browser-e10s-Support

Status

Team

Open issues/risks

`

Stage 1: Definition

1. Feature overview

In addition to the work we are doing to ensure that add-ons created with the Add-on SDK will run in their own processes to ensure better perfomance, there may be elements included in these add-ons which will need to run in one of the other processes, most specifically, the content process. For example, when the add-on accesses content we must ensure that is passed to the content process. This may also mean that page-mods (the modification of web pages - think "greasemonkey") will have to run in a different process than the add-on process.

This continues the work to ensure that Firefox performance is optimal and supports the emerging Electrolysis work.

2. Users & use cases

As with the work to make add-ons written with the Add-on SDK run in their own process, this should work with no input from the developer at all. While we want the developer to know that this is being done for her, she need not do any extra work for the elements she's using to run in the correct processes.

3. Dependencies

The feature depends on platform support (specifically the Electrolysis work) for loading and executing the correct elements into the correct processes.

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