Closed Bug 1239361 Opened 4 years ago Closed 2 years ago
Mouse-over selects from search suggestions on about:home
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 Build ID: 20160105164030 Steps to reproduce: Navigate to about:home. Enter a search, but select a search engine other than your default (which is a wiki or dictionary lookup in some versions). Mouse-over of suggestions other than your search will change your search, and given the position of the alternate search-engine buttons, it's awkward not to have your search changed. Actual results: Incorrect search requested from Wikipedia or the Dictionary you wanted to use. Expected results: Expect this to function in the same way as the toolbar searchbox, in that only a click will change what is in the text field; therefore, what you are searching.
Severity: normal → major
OS: Unspecified → Windows 10
consistency bug for suggestions and about:home page
Severity: major → minor
Priority: -- → P2
Whiteboard: [fxsearch] consistency
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: P2 → P3
It appears that this has been fixed, or at least it's fixed as of v58. That is to say, when a search on the search bar (whether it's the one on about:home/about:newtab or the toolbar) is triggered with a press of the Enter key, the resulting search will be for the text shown in the search bar (whether it was typed in or picked from the suggestion list with arrow keys), never the drop-down suggestion the mouse is hovering over or the one it hovered over last. Also, when triggering a search by clicking on the "Search" arrow button or clicking the icon of a one-off search provider, the search will be for the text shown in the search bar as well. And when clicking on a drop-down suggestion, the clicked on suggestion is always what's searched for, no matter what text is in the search box.
Yep, it looks WFM.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.