On Fri, Dec 16, 2011 at 3:08 PM, Peter Kasting wrote:
> >
> > On Tue, 17 May 2011, Bjartur Thorlacius wrote:
> > > Then why add an API when we've already got (IMO superior) declarative
> > > markup?
> >
> > In the case of adding the API to the spec, because it's already
> > implemented. As to why
On Fri, Dec 16, 2011 at 3:08 PM, Peter Kasting wrote:
>
> As for AddSearchProvider(), I know one reason it was added to Chrome was
> explicitly to expose the "and make default" functionality.
>
I've been informed that the "set default" part is going away in Chrome 17+
anyway, so since that will l
>
> On Tue, 17 May 2011, Bjartur Thorlacius wrote:
> > Then why add an API when we've already got (IMO superior) declarative
> > markup?
>
> In the case of adding the API to the spec, because it's already
> implemented. As to why it was added to the browsers, no idea.
Certainly there's no declara
On Mon, 16 May 2011, Adam Shannon wrote:
> On Mon, May 16, 2011 at 18:39, Ian Hickson wrote:
> > On Mon, 16 May 2011, Adam Shannon wrote:
> >>
> >> I don't like having the only barrier between changing the default
> >> search engine for a user's browser be a single dialog box. This list
> >> (an
On 5/16/11, Ian Hickson wrote:
> On Mon, 16 May 2011, Adam Shannon wrote:
>> I'd rather see UA's implement better controls on their end than see an
>> API which could be largely abused. (Drag and drop browser controls over
>> tons of sites asking for permission to be the default.)
>
> I agree. Not
On Mon, May 16, 2011 at 18:39, Ian Hickson wrote:
> On Mon, 16 May 2011, Adam Shannon wrote:
>>
>> I don't like having the only barrier between changing the default search
>> engine for a user's browser be a single dialog box. This list (and
>> others) have repeatedly found that dialogs don't work
On Mon, 16 May 2011, Adam Shannon wrote:
>
> I don't like having the only barrier between changing the default search
> engine for a user's browser be a single dialog box. This list (and
> others) have repeatedly found that dialogs don't work and users skip
> past them.
>
> Think of the non-te
On Mon, May 16, 2011 at 18:29, Ian Hickson wrote:
>> 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.
>
> I haven't specifie
On Mon, 14 Feb 2011, David Levin wrote:
>
> 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,
> This should be rare as annoying and confusing your users typically isn't a
> good business strategy.
Not all strategies involve wanting to keep normal, happy, satisfied customers.
Spammers and other fraudsters seem to be perfectly happy with things
where they capture things like the default sea
On 2/16/11, David Levin wrote:
> On Tue, Feb 15, 2011 at 9:42 AM, Bjartur Thorlacius
> wrote:
>
>> > 2. When a user decides to use it, they have to follow a set of complex
>>
>> instructions (http://www.google.com/search?q=switch+default+search+engines
>> )
>> >
>> Annoying implementation issue. h
On Tue, Feb 15, 2011 at 9:42 AM, Bjartur Thorlacius wrote:
> > 2. When a user decides to use it, they have to follow a set of complex
>
> instructions (http://www.google.com/search?q=switch+default+search+engines
> )
> >
> Annoying implementation issue. http://bugzilla.mozilla.com/enter_bug.cgi
>
* Kornel Lesi?ski wrote:
>Change of default search engine may have security implications — there are
>less tech-savvy people who rely on search engine for *everything* they do
>on the net and blindly trust the results (see famous "facebook login"
>case).
(There are in fact many people who do
On Mon, 14 Feb 2011 21:34:27 -, David Levin wrote:
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
default.
* 0 otherwise
If the given url doesn’t hav
On 2/14/11, David Levin wrote:
> Problem
> 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, t
Problem
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 sear
16 matches
Mail list logo
