© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
(In reply to comment #15)
> (In reply to comment #14)
> > Created an attachment (id=230808) [edit]
> > work in progress
>
> For clarity, is what you're implementing the last paragraph of comment 11?
> That's sort of what the patch looked like, but I didn't actually try using it.
>
The last paragraph of comment #11 has too many 'if' clauses in it for me to respond with a simple 'yes' or 'no.' What we're doing here is:
a.) A 'Default' button that users can set in the search-engine manager. This will set the userDefaultEngine attribute to that engine. Normally, userDefaultEngine points to defaultEngine.
b.) When the user does things like context-menu search, or serching from Tools without the search box visible, we'll now get userDefaultEngine instead.
My biggest concern here is that it's nearly impossible to describe what this 'default' button does in any concise form. I think it's just going to confuse users.
The above plan was largely based off of comment #4, but I still think the drawback of that proposal is that we don't make it clear to the user what they're choosing. I'd really like to get some more feedback from the user-experience folks here.