[whatwg] Proposal for IsSearchProviderInstalled / AddSearchProvider
levin at chromium.org
Mon Feb 14 13:34:27 PST 2011
Although the default search provider may have a significant impact on a
user’s web experience, it isn’t easy for users to set this.
Ideally, a search engine should be able to offer the user the ability to
easily use it as the default. Currently, there are two obstacles to this:
1. The search engine may not be able to detect that it already is the
default, so it would offer this too broadly.
2. When a user decides to use it, they have to follow a set of complex
Add two apis to window.external:
IsSearchProviderInstalled(string url) returns
* 2 if the origin in the given url is the default search provider
* 1 if the origin in the given url is a search provider but not the
* 0 otherwise
If the given url doesn’t have the same security origin as the page, this api
throws an access denied exception. (This makes the url redundant but it is
kept to be consistent with the method exposed by IE 7.)
AddSearchProvider(string openSearchUrl, [optional] bool asDefault) retrieves
the open search document from openSearchUrl and decides in a UA specific
manner whether to prompt the user about the change or addition.
Doesn’t this already exist?
Both of these api’s are present in IE7 (and later) except for the additional
argument to AddSearchProvider (asDefault) and a change in the url's that may
be queried. The pair of apis aren’t in a standard or many of the other
Won’t the InstallSearchProvider api get abused?
The home page setting for users has a similar value. Yet, the SetHomePage
api available in IE does not seem to be abused significantly. Largely this
will depend on the UA providing appropriate measures to protect users. In
Chromium, we rely on a combination of user gesture (click, etc.) plus a
dialog which clearly explains what is going to happen with the default being
that nothing is changed (
More information about the whatwg