Closed
Bug 1202800
Opened 10 years ago
Closed 10 years ago
Limit items on "Add more search engines…" page to only search one-click search engines.
Categories
(Firefox :: Search, defect)
Firefox
Search
Tracking
()
RESOLVED
INVALID
People
(Reporter: rfeeley, Unassigned)
Details
In Firefox Search Preferences, when the user clicks "Add more search engines…" they are taken to a page with thousands of results. This should be limited to one-click search engines to prevent users from inadvertently adding search toolbars and other unwanted add-ons to Firefox.
Comment 1•10 years ago
|
||
Ryan, I'm not sure what you mean. There's nothing special about one-click engines; any engine can be one-click. When you add an engine, it appears in the list in the Search pref pane, and then you can check it to make it a one-click engine or uncheck it to not.
Flags: needinfo?(rfeeley)
| Reporter | ||
Comment 2•10 years ago
|
||
Are there really 3,470 engines that can be added to the search bar? (and allmusic isn't one of them?).
Flags: needinfo?(rfeeley) → needinfo?(adw)
Comment 3•10 years ago
|
||
According to AMO, yeah. Anybody can make one for any site and post it to AMO (after it's been reviewed like all add-ons are, I assume, but maybe not). If nobody made one for allmusic and posted it to AMO, then there won't be one on AMO.
Do you want to morph this bug into something else like a better UI in the pref pane? If it confused you and you're a UX person, maybe it's not such a great UI. Otherwise we should probably close this.
Flags: needinfo?(adw) → needinfo?(rfeeley)
| Reporter | ||
Comment 4•10 years ago
|
||
Good answers, thanks! I'll close it. Luckily some of the add-ons folks are in town, and I'll make sure we discuss search engines. Currently, I don't think the search engines are accurately indicated in the store (there should be a facet on the left at the very least). And really this is more of an AMO bug than Firefox.
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(rfeeley)
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•