Closed Bug 1584111 Opened 5 years ago Closed 2 years ago

Search installed Add-Ons / Extensions

Categories

(Toolkit :: Add-ons Manager, enhancement, P3)

enhancement

Tracking

()

RESOLVED DUPLICATE of bug 1499500

People

(Reporter: LOFK, Unassigned)

References

Details

Attachments

(1 file)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:69.0) Gecko/20100101 Firefox/69.0

Expected results:

Ability to search installed add-ons / extensions.

Even searching the installed extensions using Ctrl+F has been disabled by re-routing it to searching AMO.

Component: Untriaged → Add-ons Manager
Product: Firefox → Toolkit

Currently our search entry searches amo. Wondering if there's some way to add local search. (Maybe a context toggle on the search?)

Flags: needinfo?(abenson)
Priority: -- → P3

For posterity, that search box in about:addons used to search local addons as well and that was removed in bug 1263313.

See Also: → new-amo-search

Now that this page is in HTML we could potentially filter out cards that don't match the search. Here's a quick example I did. A few edge cases to work out like switching views (I guess clear search when that happens) and the possible confusion of hitting enter out of habit expecting a local search and ending up on AMO.

Flags: needinfo?(abenson)

Because of the sidebar, bug 1658601, scrolling about:addons can trigger my migraines, so searching would be an accessible alternative.

And command-f/control-f page search gets redirected to addons.mozilla.org search.

I've found a workaround finally and I don't need to scan across my fifty addons for something I don't remember the exact starting letter of its name:

In a normal tab, type Ctrl-F to bring up the search bar, and then in the same tab, type in urlbar to visit about:addons. The search bar will remain there and works.

Wait so this was originally opened 2 years ago with Bug 1516227 No option to "search installed extensions", but that was closed incorrectly with being a duplicate of "Bug 868705 Add a dropdown menu near about add-ons search for searching all add-ons(default), the current section, or all of your add-ons" Since that was an 8 year old bug that was basically the XUL version of Firefox....

Why was
Bug 1263313 Change the search in add-ons manager to use just AMO search
created in the first place?! Who did this convenience? if I want new add-ons I go to get new add-ons, I don't go to my settings page with all my current ones unless I'm trying to load one not from the store. The worse part is, you could just enable ctrl+f on the page and I wouldn't care so much. But it's disabled for some reason.

(In reply to Chris Royer from comment #7)

Wait so this was originally opened 2 years ago with Bug 1516227 No option to "search installed extensions", but that was closed incorrectly with being a duplicate of "Bug 868705 Add a dropdown menu near about add-ons search for searching all add-ons(default), the current section, or all of your add-ons" Since that was an 8 year old bug that was basically the XUL version of Firefox....

Why was
Bug 1263313 Change the search in add-ons manager to use just AMO search
created in the first place?! Who did this convenience? if I want new add-ons I go to get new add-ons, I don't go to my settings page with all my current ones unless I'm trying to load one not from the store. The worse part is, you could just enable ctrl+f on the page and I wouldn't care so much. But it's disabled for some reason.

Oh Apparently there's also 1499500 I found in my post history.

Why was Bug 1263313 Change the search in add-ons manager to use just AMO search
created in the first place?!

Apparently because the poster and he devs didn't find search useful. But they also broke scrolling, so search would be even more useful. If they break page down, too, there will be no accessible way to check add-ons.

Note that some devices lack page down.

Flags: needinfo?(lambeaceh22)
Flags: needinfo?(stolenwings13)
Flags: needinfo?(stolenwings13)

Redirect a needinfo that is pending on an inactive user to the triage owner.
:mixedpuppy, since the bug has recent activity, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(lambeaceh22) → needinfo?(mixedpuppy)

There is no reason at the moment for the default Ctrl+F bar to be disabled on this page, as there is no other way to search for the content of this page.
In my opinion, as the search field doesn't search inside of the currently open page, Ctrl+F should open the default find bar and not redirect to this field.

Bug 1499500 has more discussion and a suggestion for how to fix this. Duping

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Flags: needinfo?(mixedpuppy)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: