3 ms·
Lots of comments in this thread about why they have implemented this before implementing addons. Based on Mozilla's public project board it looks like they are
by calpaterson 7y ago
Lots of comments in this thread about why they have implemented this before implementing addons. Based on Mozilla's public project board it looks like they are well underway on implementing add-ons:
https://github.com/orgs/mozilla-mobile/projects/44 https://github.com/orgs/mozilla-mobile/projects/44
Check the done column
- pwg 7y agoThe comments here re. "why before addons" is because the marketing-speak (tm) blog post leaves everyone with the impression that this new version is just about to replace the existing FF for Android that does support uBlockOrigin. And as many comments here indicate (and I am with those who feel this way), for a huge swath of FF for Android users, the ability to have uBlockOrigin is the critical reason why they have FF for Android installed in the first place. As in, if there is no uBlockOrigin, there is no remaining compelling reason to run FF for Android. This is a failure of the mozilla marketing droids to understand their customers.
- calpaterson 7y ago> the ability to have uBlockOrigin is the critical reason why they have FF for Android Me too Agreed that the blog post is dross. I still hold out hope though that Mozilla is not as dumb as their dumbest blogpost :)