Features/Desktop/Enhanced Customization APIs
|Enhanced Customization APIs|
|Product manager||Asa Dotzler|
|Directly Responsible Individual||Jorge Villalobos|
|Lead engineer||Gavin Sharp|
|Product marketing lead||`|
|Additional members||Matt Grimes, Tyler Downer, Michael Verdi|
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.
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.
External installers should also have the possibility of using these APIs. Some make these setting changes without installing add-ons.
Stage 2: Design
5. Functional specification
6. User experience design
Stage 3: Planning
7. Implementation plan
Quality Assurance review
Stage 4: Development
Stage 5: Release
10. Landing criteria
|Theme / Goal||`|
Team status notes