canmove, Confirmed users
1,448
edits
Features/Desktop/Enhanced Customization APIs: Difference between revisions
Features/Desktop/Enhanced Customization APIs (view source)
Revision as of 18:06, 12 October 2012
, 12 October 2012no edit summary
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
|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. | |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 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. | ||
|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 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 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. | ||