User Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:23.0) Gecko/20100101 Firefox/23.0 (Beta/Release) Build ID: 20130730113002 Steps to reproduce: Used the new feature of FF v23 : home page search, available for any kind of search engine (at least the ones selected in the search box). Actual results: While the Google icon was displayed at the left of the search field on the home page, none of the other search engine icons were available (while they were in fact available in the box at the top right corner). Expected results: All search icons should have been available.
I think this is by design for the moment.
Indeed, we have no larger icons to use for arbitrary "other" engines. Using the smaller favicon would be possible, but might look somewhat strange.
Status: UNCONFIRMED → NEW
Component: Untriaged → General
Ever confirmed: true
OS: Windows 8 → All
Hardware: x86_64 → All
Summary: Small icons displayed in the search box (top right corner) are not used in the "home page search" (Firefox default) → no icon displayed on about:home when custom search engine is selected
Thanks Paul and Gavin for your feedback. In my humble opinion, if the larger version of the icons are not available, the current UI design could still be improved by simply synching the two query fields. In fact, for the moment, when I select another search engine in the top-right drop-down menu displaying the small icons, the opened about:home page is not reloaded, therefore leading to the selection of two different search engines (when the about:home page is reloaded manually by the user, this is no longer true, of course). Thanks in advance for your help!
(In reply to David Bourguignon from comment #3) > In fact, for the moment, when I select another search engine in the > top-right drop-down menu displaying the small icons, the opened about:home > page is not reloaded That would be another issue. Gavin, should this be treated separately ?
(In reply to Paul Silaghi [QA] from comment #4) > (In reply to David Bourguignon from comment #3) > > In fact, for the moment, when I select another search engine in the > > top-right drop-down menu displaying the small icons, the opened about:home > > page is not reloaded > That would be another issue. Gavin, should this be treated separately ? This is fixed in bug 860119, which is riding the train to 24. David, if you can confirm that you're not using Fx 24, then we have the cause & solution!
Thanks Paul and Mike for the follow-up. Mike, I do confirm that I am not using Fx v24 but still v23.0.1. However, I think this Bug 904067 report should still be valid since it mentions first the missing search engine icon issue... Thanks in advance!
(In reply to David Bourguignon from comment #6) > However, I think this Bug 904067 report should still be valid since it > mentions first the missing search engine icon issue... Thanks in advance! I think so too! I meant that there's no need to file a separate bug for about:home not updating right away when you select a different search engine from the dropdown, because bug 860119 is all about that.
How can I get back keyword.url functionality? I had a custom DuckDuckGo search set up as my default, and now none of my customizations work. Keyword.url does nothing, the only way to change my default search engine is via the search bar, which doesn’t allow for search customization, only the default DuckDuckGo. This is really terrible. Why did you disable this functionality? I tried to comment on the original thread but now you’ve disabled commentary on that as well? What is going on with Mozilla?
@Dawn: I am not an expert on the topic, but I would say this is now the default behaviour. Search engines are selected in the search bar. Only a few of them (none?) allow search customization. I encourage you to open a new "bug report" (it should be rather named a "functionality requirement" in this case) explaining that you would like to have the possibility to setup search preferences for each search options in the search bar... Hope this helps!
Dawn: you can find various alternatives/ workarounds mentioned in the comments on bug 738818. I hope you'll find what you're looking for there!
You need to log in before you can comment on or make changes to this bug.