I want to put some filter when I search AMO to exclude all legacy extensions. I’m using Nightly and v57 is right around the corner. I want to migrate away from all my legacy addons and such a filter would really help out.
Is this possible?
Thank you!
jorgev
March 28, 2017, 7:16pm
2
It’s not possible at the moment. We will be adding a label to highlight WebExtensions on the site soon, but we don’t plan to introduce a search filter for it.
Can you automatically tag them just like JPM got tagged?
jorgev
March 28, 2017, 8:30pm
4
Yeah, we’re considering it.
There’s something like a search, but it’s not intuitive if beginning at https://addons.mozilla.org/
Adapted from https://github.com/mozilla/addons-server/issues/4974#issuecomment-297956280 , as far as I can tell:
https://addons.mozilla.org/firefox/search/?tag=firefox57
disclose the list of categories
select one.
Result:
everything with that tag in that category.
When it’s not desirable to list everything:
is it possible to search?
Doing so loses context. After each new search is performed with the search field, it’s necessary to reapply a tag.
Example
Add-ons tagged with firefox57 – Add-ons for Firefox (en-US)
in the search field, change the phrase from count to sum
Return or Enter
Expected
sum -related extensions in the Tabs category that are compatible with both Firefox 54 and Firefox 57, excluding extensions that are incompatible with 57
Actual result
sum -related extensions in the Tabs category that are compatible with Firefox 54, including extensions that are incompatible with 57.
Can this be fixed, to make searching more intuitive for other end users?
(For myself, I’ll learn to manually edit the URL without relying on the GUI alone.)
I guess, things will become less frustrating when we gain the combination of this –
opened 09:59PM - 19 Aug 17 UTC
closed 09:22AM - 19 Sep 17 UTC
qa:not_needed
component:api
repository:addons-server
The new search mocks include a switch to include only featured add-ons, but the … current search API doesn't support returning only featured add-ons.
Maybe this is unclear or really tough to implement and I think it's a bit of a strange feature anyway. Would this be a tough option to add to the [Search API](http://addons-server.readthedocs.io/en/latest/topics/api/addons.html#search)?
See: https://github.com/mozilla/addons/issues/10673
– plus the work towards removal of legacy add-ons from all featured collections.
In the meantime, there’s this (click to spin):
Thanks, Washing Machine for excellent use of WebExtensions APIs.
Warped sense of humour aside … it will be genuinely lovely to have the majority greyness disappear from collections such as this:
Last but not least, for non-featured collections:
opened 01:25AM - 30 Aug 17 UTC
closed 02:30PM - 10 Sep 19 UTC
component:api
state:stale
repository:addons-server
`project: firefox 57 compatibility`
## Enhancement request
At https://gith… ub.com/mozilla/addons/issues/4167 (2017-06-03) under _Add label to listing pages to highlight WebExtensions · Issue `#4974` · mozilla/addons-server_, @erosman wrote:
> Collections could also benefit from the tag
Additionally, it should be possible to:
- exclude legacy items
– in other words, **filter by compatibility**.
If not filter, then please at least allow readers to **sort by compatibility**.
## For now, in the absence of tags
I use multiprocess-compatible [User Agent Overrider](https://addons.mozilla.org/firefox/addon/user-agent-overrider/) to quickly set or unset an appropriate string.
### Examples
https://addons.mozilla.org/en-GB/firefox/collections/Firebreathing/h/?sort=added (a _Hidden Gems!_ collection), without then with an override:

`Mozilla/5.0 (X11; FreeBSD amd64; rv:57.0) Gecko/20100101 Firefox/57.0`

[A more popular collection](https://addons.mozilla.org/en-GB/firefox/collections/davy-jones/optimizefirefox/?sort=popular) (6,284 followers), sorted by popularity, exemplifying the current likelihood of promotion of legacy items, without attention to compatibility –

– then with:

I wondered whether the FreeBSD/Linux aspect of my `general.useragent.override` was skewing things, so I switched to:
`Windows / Firefox 57: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:57.0) Gecko/20100101 Firefox/57.0`
– then browsed all nine pages of that popular collection. Not one green display of compatibility `</cough> ;-)`
–and popular https://addons.mozilla.org/firefox/collections/davy-jones/optimizefirefox/?sort=popular (129 extensions), which seems to be one hundred percent incompatible with WebExtensions, which is why I maintain a warped sense of humour. Note for reviewer’s diaries: 2018-04-01 – make optimized firefox a featured collection :-)
For reference only
Disable all legacy add-on files · Issue #9472 · mozilla/addons-server was closed (verified fixed in October 2018) and became effective in November 2018.
Flip-sides (seeking legacy add-ons)