Open Bug 1817614 Opened 2 years ago Updated 1 year ago

addon collection is limited to 50 addons maximum (hardcoded limit)

Categories

(Firefox for Android :: WebExtensions, enhancement, P3)

Firefox 110
All
Android
enhancement

Tracking

()

People

(Reporter: efreak2004, Unassigned)

Details

User Agent: Mozilla/5.0 (Android 10; Mobile; rv:102.0) Gecko/102.0 Firefox/102.0

Steps to reproduce:

Added an addon to my collection (configured via custom addon collection preference)

Actual results:

The list of addons available in the addons menu did not change to include the new addon. (Tested in Mull, official Firefox Nightly)

Expected results:

The new addon should have been displayed

Filling out the form did not provide me a place to add more details. This limit is hardcoded in AddonCollectionProvider.kt. My extension collection formerly had a number of addons, far more than 50, despite my not using all of them, as I frequently add once to test it out. Beyond this, I still have a number of addons that I keep installed but disabled most of the time, and only enable when needed. It's frustrating that in order to try a new addon that might fix a problem, I have to check all my browsers to find an addon that's safe to remove from my list.

The limit on addons should be set either ridiculously high (500), or the code should be updated to fetch subsequent pages as well.

The severity field is not set for this bug.
:cpeterson, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(cpeterson)
Severity: -- → N/A
Status: UNCONFIRMED → NEW
Type: defect → enhancement
Ever confirmed: true
Flags: needinfo?(cpeterson)
Priority: -- → P3

Thanks for reporting this issue. We're looking to see what UI work would be needed to remove the hardcoded limit.

Imagine if you could just install addons from amo website directly instead of having to do the collection dance (which also is potentially privacy invading)... 🙄

You need to log in before you can comment on or make changes to this bug.