Comment 35 for bug 526453

In Aurora (version of 5 dec 2011) I have still the same problem.

I really don't care of whatever default is set on a new profile. All I want is a way to set it easily and error-free from an UI.

Right now, we have to change the pref browser.search.defaultenginename in about:config, and if we set it to an unknown value (like "bing" instead of "Bing"), the default search is broken. This is wrong.

I feel using the current selected search engine is not a good option here: there's really no point at having a search bar if we do this. If my last search was on ebay, amazon or wikipedia, I don't want to have my default search to go there, I want my default to go to whatever default is set.

To me, 2 options would be appropriate :
- either: the first search engine of the list is the default
- or: the user can set it using a "set default" button. Then take care to put a sensible default if this search engine is gone. This could also be done for any option, when "browser.search.defaultenginename" is set to a wrong value. Another bug maybe ?

Either way, make it apparent in the UI, like make it bold with (default) after its name.

And I can think of a third solution :

- replace the empty keyword values by a null/undefined value which would be written as "none". Then, the real empty ("") would be for the default search. It makes sense because, really, that is what seems to happen. But from the user point of view it's maybe difficult to understand.

Thanks