Confirmed users
2,492
edits
Program Management/Projects/SearchHijacking: Difference between revisions
Program Management/Projects/SearchHijacking (view source)
Revision as of 05:45, 10 February 2012
, 10 February 2012→Hardening keyword URLs
| Line 30: | Line 30: | ||
* Extensions that change this value properly (by shipping a different default pref as opposed to programmatically setting the pref) also wouldn't be affected by this. | * Extensions that change this value properly (by shipping a different default pref as opposed to programmatically setting the pref) also wouldn't be affected by this. | ||
* Users who manually change the value voluntarily can just ignore the prompt (very small minority). | * Users who manually change the value voluntarily can just ignore the prompt (very small minority). | ||
* We should also be clear about which users we're talking about prompting. The only way to get a user-set value for keyword.URL is: | |||
** Manually change the pref in about:config (or prefs.js in your profile) | |||
** Install an extension that programmatically sets the pref (rather than changing the pref in the "supported" way, by shipping a new pref default) | |||
** Have a third-party installer set the pref in your profile's prefs.js | |||
* We will extend this to all languages builds. We thought of doing en-US only at first but see no real reason to do this. | * We will extend this to all languages builds. We thought of doing en-US only at first but see no real reason to do this. | ||