© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
(In reply to comment #2)
> This seems like a pretty serious usability regression. Is there a reason we're
> ignoring the user's prefs like this?
There is no user pref for "engine to use with the search bar hidden". There is a user pref for "selected engine in the search bar", and a hidden "default engine" pref. It was decided when this was changed that using the "default engine" is better than using the engine that was last selected when the search bar was visible. The plan was to include some way of setting the "default engine". I'm not sure that just using the current engine would solve any of the problems: that would mean people who had hidden the search bar using 1.5 will be "stuck" with the last-selected engine when they upgrade to Firefox 2, and it won't necessarily be obvious for them that to select a new engine they need to unhide the search bar.
This is a front-end change that was made on both the 1.8 branch and trunk, so I'm not sure what relevance the blocking1.9a1? flag has. I think this should block Firefox 2.