Program Management/Projects/SearchHijacking: Difference between revisions

Line 25: Line 25:
==Hardening keyword URLs==
==Hardening keyword URLs==
* We are going to prompt everyone we see who has changed keyword.URL to a user-set value.  
* We are going to prompt everyone we see who has changed keyword.URL to a user-set value.  
** On search the users will be prompted when we detect the change and be presented with a notification prompt.
* On search the users will be prompted when we detect the change and be presented with a notification prompt.
** We can have the prompt only include "Yes, reset" and "No, don't ask again" buttons (exact text still TBD), and keep showing the notification bar on searches until we get one of those responses.
* We can have the prompt only include "Yes, reset" and "No, don't ask again" buttons (exact text still TBD), and keep showing the notification bar on searches until we get one of those responses.
** The Bing builds we distribute wouldn't be affected by this (their default value is different, it's not "user-set").  
* The Bing builds we distribute wouldn't be affected by this (their default value is different, it's not "user-set").  
** 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 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.


==Bugs/Tracking==
==Bugs/Tracking==
Confirmed users
2,492

edits