canmove, Confirmed users
1,448
edits
Features/Desktop/Enhanced Customization APIs: Difference between revisions
Jump to navigation
Jump to search
Features/Desktop/Enhanced Customization APIs (view source)
Revision as of 23:15, 8 March 2013
, 8 March 2013no edit summary
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
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. | 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 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. | ||