Confirmed users
834
edits
AwesomebarSearchProviderReset/TestPlan: Difference between revisions
Jump to navigation
Jump to search
AwesomebarSearchProviderReset/TestPlan (view source)
Revision as of 15:14, 8 January 2013
, 8 January 2013→Summary
| Line 16: | Line 16: | ||
== Summary == | == Summary == | ||
Users falling victim to "search hijacking" (keyword.URL being taken over by an unwanted search engine) is a common problem. | |||
There are two cases we can detect: | |||
*pref is changed, and the hostname is different (e.g. switched from the default of Google to SuperAwesomeWebDealsSearch.com) | |||
*pref is changed, and only parameters are different (e.g. user customized to a specific type of Google search, or referral codes where added) | |||
In either case, we could prompt the user and offer to reset the keyword.URL value to the default after they trigger a search from the location bar. | |||
== Reference == | == Reference == | ||