Features/Desktop/Enhanced Customization APIs
Status
| Enhanced Customization APIs | |
| Stage | Draft |
| Status | ` |
| Release target | ` |
| Health | OK |
| Status note | ` |
{{#set:Feature name=Enhanced Customization APIs
|Feature stage=Draft |Feature status=` |Feature version=` |Feature health=OK |Feature status note=` }}
Team
| Product manager | Asa Dotzler |
| Directly Responsible Individual | Jorge Villalobos |
| Lead engineer | Gavin Sharp |
| Security lead | ` |
| Privacy lead | ` |
| Localization lead | ` |
| Accessibility lead | ` |
| QA lead | ` |
| UX lead | ` |
| Product marketing lead | ` |
| Operations lead | ` |
| Additional members | Matt Grimes, Tyler Downer, Michael Verdi |
{{#set:Feature product manager=Asa Dotzler
|Feature feature manager=Jorge Villalobos |Feature lead engineer=Gavin Sharp |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=Matt Grimes, Tyler Downer, Michael Verdi }}
Open issues/risks
`
Stage 1: Definition
1. Feature overview
We need to provide a way for add-on developers to change user settings that make it easier for users to make an informed decision, and also make it easier for the settings to be reverted when the add-on is removed.
The settings that need to be protected are: homepage, new tab page, default search engine and keyword URL. The User Agent string might need this too, but we need to consider some add-ons are designed to change the UA and we wouldn't want nagging dialogs every time it is changed.
- See bug 738818 - Consolidate Firefox search preferences.
2. Users & use cases
This is an add-on developer API, but it also affects users who install add-ons that change these settings.
3. Dependencies
Before release, we need to make sure that we communicate this feature to all developers, specially those who don't list their add-ons on AMO. We need to have a policy of not accepting any bypassing of these new APIs.
4. Requirements
External installers should also have the possibility of using these APIs. Some make these setting changes without installing add-ons.
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=We need to provide a way for add-on developers to change user settings that make it easier for users to make an informed decision, and also make it easier for the settings to be reverted when the add-on is removed.
The settings that need to be protected are: homepage, new tab page, default search engine and keyword URL. The User Agent string might need this too, but we need to consider some add-ons are designed to change the UA and we wouldn't want nagging dialogs every time it is changed.
- See bug 738818 - Consolidate Firefox search preferences.
|Feature users and use cases=This is an add-on developer API, but it also affects users who install add-ons that change these settings. |Feature dependencies=Before release, we need to make sure that we communicate this feature to all developers, specially those who don't list their add-ons on AMO. We need to have a policy of not accepting any bypassing of these new APIs. |Feature requirements=External installers should also have the possibility of using these APIs. Some make these setting changes without installing add-ons. |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 | ` |
| Secondary roadmap | ` |
| Feature list | ` |
| Project | ` |
| Engineering team | ` |
{{#set:Feature priority=Unprioritized
|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 | ` | ` |
| 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=` }}