Features/Jetpack/Browser-e10s-Support
Status
| Browser-e10s-Support | |
| Stage | Shelved |
| Status | ` |
| Release target | ` |
| Health | OK |
| Status note | e10s is shelved |
{{#set:Feature name=Browser-e10s-Support
|Feature stage=Shelved |Feature status=` |Feature version=` |Feature health=OK |Feature status note=e10s is shelved }}
Team
| Product manager | David Mason |
| Directly Responsible Individual | ` |
| Lead engineer | ` |
| Security lead | ` |
| 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=` |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
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
` {{#set:Feature open issues and risks=` |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. |Feature users and 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. |Feature dependencies=The feature depends on platform support (specifically the Electrolysis work) for loading and executing the correct elements into the correct processes. |Feature requirements=` |Feature non-goals=` |Feature functional spec=` |Feature ux design=` |Feature implementation plan=` |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 | Unprioritized |
| Rank | 999 |
| Theme / Goal | ` |
| Roadmap | Jetpack |
| Secondary roadmap | ` |
| Feature list | Jetpack |
| Project | ` |
| Engineering team | Jetpack |
{{#set:Feature priority=Unprioritized
|Feature rank=999 |Feature theme=` |Feature roadmap=Jetpack |Feature secondary roadmap=` |Feature list=Jetpack |Feature project=` |Feature engineering team=Jetpack }}
Team status notes
| status | notes | |
| Products | ` | ` |
| Engineering | ` | ` |
| Security | ` | ` |
| 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=` |Feature security health=` |Feature security notes=` |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=` }}