Waterfox: AMO add-on/extension search results at (in) about:addons

Created on 1 Mar 2019  Â·  5Comments  Â·  Source: MrAlex94/Waterfox

image

– _Could not find any matching add-ons_

From IRC:

Re: https://www.reddit.com/r/waterfox/comments/atwjys/-/ehhf79p/ might a v3 or v4 API string allow search results to be returned in ye olde about:addons GUI?

yes, but it's not just the url that's changed - the developers will need to update the code to handle the newer v3+ api https://addons-server.readthedocs.io/en/latest/topics/api/index.html
(or https://addons-server.readthedocs.io/en/latest/topics/api/v3_legacy/index.html#v3-api-index)

@MrAlex94 I'm closing this, assuming _wontfix_ but please reopen if you feel the need for the enhancement.

Most helpful comment

If that search interface can no longer work, then it should probably should be removed or an alternative provided (such as a link to the add-ons site). I was trying to use it just now and couldn't figure out what was going on. From a user perspective, that's confusing.

All 5 comments

If that search interface can no longer work, then it should probably should be removed or an alternative provided (such as a link to the add-ons site). I was trying to use it just now and couldn't figure out what was going on. From a user perspective, that's confusing.

Good shout. Should replace it with the classic add-on archive :-)

On Wed, 6 Mar 2019 at 00:21, Travis Evans notifications@github.com wrote:

If that search interface can no longer work, then it should probably
should be removed or an alternative provided (such as a link to the add-ons
site). I was trying to use it just now and couldn't figure out what was
going on. From a user perspective, that's confusing.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MrAlex94/Waterfox/issues/873#issuecomment-469913913,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEgoWJZ53VNI_v-j2ma1qFcI5AQyVOPyks5vTwoOgaJpZM4bZiZA
.

@ticalc-travis true. Sorry. My _wontfix_ assumption was based on available (human) resources for other interfaces that mislead the end user:

… like, I'm a human resource but if I were to attempt pull requests for issues such as those, I'd make a _horrible_ mess :-/


@MrAlex94 aiming to return CAA results at which of these two addresses?

  1. about:addons in the same tab
  2. caa:list?q=_search string_ in a new tab

Either way, the find interface (prior to gaining results) should make clear that it'll be an unusual search. Even if you make it explicit, expect some users to use the search box without paying attention; risk of ending up with an outdated extension without the user realising that there's a more recent version.

FWIW I prefer either of the other options,

… removed or … a link to the add-ons site. …

– and for the latter, the link should be non-localised https://addons.mozilla.org/

Note, the caa: reference to the live site is localised and IIRC (I can't find the relevant issue) will not be de-localised.

Meta/tracking: #538

Yeah, when I first set up Waterfox last month (migrating from the last FF ESR that still supported legacy extensions) I opted to create a fresh, new profile and might have initially just gone straight to the AMO site to download some current add-ons and then found the classic add-on archive and grabbed all the legacy stuff I needed. :-) It's possible I never tried the search box until today when I got around to recreating my alternate profile from ESR. Was puzzling, though, since I was expecting something to come up from AMO and had no idea if it ever worked before.

(BTW, I'm loving the huge performance improvement in WF over that ESR version, even after adding all my stuff back. ESR 52 was getting to where it was constantly lagging for no apparent reason, sometimes up to a minute at a time, and I was getting sick of using it.)

Improvements noted, with thanks.

Which commit removed the 🔘 Available Add-ons radio button, was it https://github.com/MrAlex94/Waterfox/commit/6d47f085ecc2dc8c59e0ae21adcb008d13e0847b?

Was this page helpful?
0 / 5 - 0 ratings