First of all sorry if this was already reported, I did not find anything and I also asked on Matrix
there are lots of extensions on addons.mozilla.org that cannot be installed
this used to work in fennec
users who used addons
Unfortunally they seem to have decided months ago that this is not a priority the best I could gather is that maybe, possibly at some point they might support this in some capacity. Meanwhile I am stuck using a version of firefox that will not be updated or be forced to not use the extensions I want. Not to mention that for the users of a extension I am a dev of we also have to tell them the same disappointing news.
Specifically this comment and the resulting discussion resulting in this statement. Basically it boils down to, what I said earlier that maybe at some point they'll allow it but they don't want to commit to it.
are you a contributor @creesch ? do you work for mozilla?
Nope, if I was I wouldn't have said "they". I am simply sharing what my experience has been so far in trying to get an answer if this will be possible at some point in the future. And so far the answer is that a vague "possibly in some capacity".
None of the other issues tackes AMO install. Now Fenix is replacing Fennec. I want an official answer, not opinions and interpretations of other issues. Sorry if I'm too blunt.
None of the other issues tackes AMO install.
They do, as it is the same issue technically speaking. The way it works before fenix is that you can only install extensions that have been signed through AMO. So the installation mechanism for AMO hosted extensions or other extensions is technically identical.
I want an official answer, not opinions and interpretations of other issues.
I understand, the statements I linked however are from a product owner at mozilla and really do comment on the same matter. In any case I do understand is that if not the sort of answer you are looking for.
Sorry if I'm too blunt.
No you just being clear, I'd also like na actual official answer that is clear on the matter.
At the very least, it would be good to have this for beta/nightly, even if it is not released to production until later. That way, we could at least help the team validate which add-ons could conceivably even be added to recommended extensions, allowing the team to follow the "letter of the law" in production.
you can test extensions with web-ext run
Duping to #11308
Sideloading sounds like a hacky way to bypass Mozilla's extension verification. That is why I reported a different issue. @liuche
We would like to expand our support to other add-ons. At this time, we don’t have details on enabling support for extensions not part of the Recommended Extensions program in the new Firefox for Android. Please follow the Add-ons Blog for future updates.
@liuche So why did you started rollout without any way to enable addons?
If the API didn't changed and addon creators can upgrade and test their addons with web-ext, then why disable them all?
Who is deciding this? And are you personally ok with this?
I've put a lot of effort into making my addons compatible with Android and I use some of them daily, so you can imagine how frustrated I feel right now...
@liuche
We would like to expand our support to other add-ons.
That is the exact same line I have seen several times. The problem is that without context it doesn't mean much at all. Does it mean more extensions are going to get verified or does it mean that at some point it will be made possible to install any signed extension like was possible before?
this should be closed
CAD is also affected, despite it seems a _Recommended Extension_.
I don't get why this hasn't been solved since February, at least for the recommended extensions. That wouldn't hurt if the update of Fenix wasn't forced recently. See also here: https://github.com/Cookie-AutoDelete/Cookie-AutoDelete/issues/758
Okok, there's ublock origin which works, but other than it reminds me a bit on mobile Chrome browsers -- excuse my sarcasm ;-)
Most helpful comment
Sideloading sounds like a hacky way to bypass Mozilla's extension verification. That is why I reported a different issue. @liuche