Open
Bug 1670185
Opened 4 years ago
Updated 1 year ago
Figure out how to manage multiple matching engines in tab-to-search
Categories
(Firefox :: Address Bar, task, P3)
Firefox
Address Bar
Tracking
()
NEW
People
(Reporter: mak, Unassigned)
References
Details
(Keywords: blocked-ux)
Currently we return only the first engine, based on search service order.
We may want to give priority to built-in, or maybe have multiple tab-to-search entries.
Reporter | ||
Comment 1•4 years ago
|
||
This is for the cases where engineA: example.com?{searchString} and engineB: example.com/images?{searchString}.
If instead we have one engine matching perfectly to the autofilled string and one matching partially, we already put perfect matches at the top.
Updated•4 years ago
|
Severity: -- → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•