Show only autosuggest results when search only engine alias is typed in the address bar

VERIFIED FIXED in Firefox 64



8 months ago
3 months ago


(Reporter: mikedeboer, Assigned: adw)


(Blocks 1 bug)

Firefox 64
Dependency tree / graph

Firefox Tracking Flags

(firefox64+ verified)


(Whiteboard: [fxsearch], URL)


(1 attachment)



8 months ago
For a visual explanation, please see Verdi's second bulleted mockup over at

If possible, we'd try and make sure that whenever a search engine alias is entered followed by keywords, to show only the autosuggest results in the AwesomeBar.


7 months ago
Assignee: nobody → adw
Priority: -- → P1
Whiteboard: [fxsearch]

Comment 1

7 months ago
[Tracking Requested - why for this release]:

Moving the tracking? flag from bug 1496772 to this bug, per bug 1496772 comment 5:

(In reply to Mike de Boer [:mikedeboer] from bug 1496772 comment #0)
> [Tracking Requested - why for this release]:
> There are a number of - should be - low effort changes to improve the search
> tiles/ keywords user interaction.
> We believe this will greatly impact the general usefulness, usability and
> users' perception of the feature when it launches in Firefox 63.

Comment 2

7 months ago
This is based on the patch in bug 1496811.

This patch looks a little worse than it probably is. (Maybe not by much.) Some of this is indentation changes, moving code around, renaming, and adding jsdocs. It looks like we missed the boat on uplifting this (and the other couple of bugs) to 63, so there's not a super-pressing need to keep the patch minimal.

PlacesSearchAutocompleteProvider assumes you're fetching suggestions from the current engine, so I had to modify it to take an engine. While I was doing that, I got a little frustrated with some of its implementation, naming, and interface. It seems like it was written to be a little more generic than it ended up being? There doesn't seem to be any need for it to return generic "match" objects instead of simply engines and `{ suggestion, historical }` objects, for example. The "defaultMatch" concept also doesn't make much sense IMO, especially with the aforementioned changes. So I made some improvements, hopefully, and I also added some jsdocs.

Comment 4

7 months ago
Pushed by
Show only search suggestion results when only an engine alias and query are typed in the address bar r=mak

Comment 5

7 months ago
Last Resolved: 7 months ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 64

Comment 6

7 months ago
Using the arrow keys to highlight a search suggestion ends up removing the search shortcut from the urlbar. Is this intentional? To be more specific:

1. Type `@google test`
2. Use down arrow key to highlight say the second suggestion

AR: urlbar says `testbook`. If I continue typing at this point, the search query is no longer being sent to Google but to my default engine.

ER: urlbar says `@google testbook` and Google remains "active." This feels more intuitive to me and allows[1] for further editing of the search query.

Also after STR1, the one-off section says `Search for @google test with:` followed by the usual list. After STR2, it says `Search for testbook with:`. Bug 1498023 will fix this, iiuc.

[1]Unsure if I'm explaining it correctly so as an example: I would like to be able to do the following:

Goal: Search Google for `telescope price`. Google is not the default engine.

Expected "lazy" steps:
i) Type `@google teles`
ii) Use down arrow to pick the `telescope` suggestion. At this point, urlbar should read `@google telescope` and continue to be in "queries being sent to Google" mode
iii) Type out ` p`. First suggestion is `telescope price`. Select it, urlbar changes to `@google telescope price`, press enter.


7 months ago
Duplicate of this bug: 1294387

Comment 8

7 months ago
Yeah, these are good points, Bruce.  I realized that the @engine text went away when you arrow down to the suggestions, but I didn't think about the fact that changing the suggestion and then selecting it would search with the default engine.  A lot of these interactions are underspecified tbh.  I'll file a new bug and mark it blocking this one.

Thanks for pointing out all the little corners where this stuff could use improvement, it's been helpful. :-)


7 months ago
Depends on: 1500516
This is verified fixed using Firefox 64.0b3 (BuildId:20181022150107) on the following OSes: Windows 10 x64, Ubuntu 18.04 x64 and macOS 10.13.
Flags: qe-verify+


3 months ago
Depends on: 1529642
You need to log in before you can comment on or make changes to this bug.