[meta] Catch up to Chrome for web search integration

UNCONFIRMED
Unassigned

Status

()

Firefox
Search
--
enhancement
UNCONFIRMED
6 years ago
3 months ago

People

(Reporter: Stephan Sokolow, Unassigned)

Tracking

(Depends on: 2 bugs)

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

6 years ago
Web search is the only place where Chrome's Omnibar is significantly superior to Firefox's AwesomeBar. The user experience is very un-polished and Firefox has three search systems (keyword.URL, quicksearch bookmarks, search plugins) which seem to be independent yet each is missing something another provides.

I think, to reach parity with Chrome, the following changes need to be made:

1. Make search engine settings editable when the search box is hidden (bug 522040 which is being worked on in bug 335781)

2. If a user types a search plugin keyword, it should appear in the awesomebar drop-down the way quicksearch bookmark keywords do (bug 782555)

3. Add a "Set As Default" button to the "Manage Search Engines" dialog to provide a UI for setting keyword.URL outside about:config (bug 782559)

4. In the longer-term, look into options to unify quicksearch bookmarks and search plugins to avoid maintaining two copies of the same functionality with two different, incomplete sets of features (bug 782562)

5. Transparently retrieve OpenSearch definitions to be stored as part of the browser history and provide an equivalent to Chrome's "Press Tab to search <most likely domain completion>" prompt. (bug 782557)
(Reporter)

Updated

6 years ago
Depends on: 335781, 782555, 782559, 782562, 782557

Updated

6 years ago
OS: Linux → All
Hardware: x86_64 → All
Version: 16 Branch → Trunk
(Reporter)

Updated

6 years ago
Depends on: 331105
No longer depends on: 782559

Comment 1

5 years ago
How about allow site:foo.com to work without thinking it is a protocol...
You need to log in before you can comment on or make changes to this bug.