And Google is probably paying Mozilla so that they block those cookies too... I think that they might have paid them for other things too... like for blocking 99% of extensions on Firefox mobile (those are speculations, that are very probable).
No, pretty much just those. There are very few extensions available on new builds of mobile Firefox.
I got excited when the blog team announced that the were more available on the nightly buil, but after jumping through loads of hoops I found out there's just a couple of new ones and most extensions are still unavailable.
The real question though is will all of them work?
If someone has a better explanation then Google paying them for doing that, please let me know. I think Mozilla's new CEO is a sock puppet like most of the sheep out there (including me sometimes).
You can install uBlock, but not uMatrix. Many many extensions are banned just because they reviewed ONE extension that they preferred for a certain usecase. For example, for OLED phone night reading, there's the most installed at the time extension "Dark Background and Light text" that offered many customizations and worked on reader mode, and more importantly redish text/links. But too bad, because Mozilla picked the one with NO settings, but a nicer icon (which is literally disney's darth vader, but who cares) called "dark reader" which only have bright blue links and white text (and despite the name do not work on reader mode), and because there is already one extension with "dark mode" they will never whitelist the others, or even provide a setting to enable it on your own.
This is a ridiculous lie, Mozilla has said repeatedly that more extensions are being enabled as support for more extension APIs are added, and it has been true. Several of my extensions which were previously disabled have come back online after updates.
Perhaps it will grow but I'll wait to see that before I believe it.
I'm still waiting very basic and popular extensions (uMatrix anyone?) for SEVERAL MONTHS.
And try to offer community help. Ha!
mozilla have to die for firefox to live.
uMatrix and uBlock share the same base code, and we have uBlock but no uMatrix... it is all so rotten. Almost like mozilla is actively breaking firefox.
They disabled many loved extensions by power users for absolutely no reason at all! after those power users spend years bending to all their capricious changes. moving to webextension? done. moving to a new mobile UI? done. But, they still want you to move to chrome no matter what.
We should take firefox out of their hands before it is too late.
The reasons were stated repeatedly. They rewrote the mobile browser engine, which broke extension API support since all of the internal APIs changed, and they didn't have the resources to support both browsers simultaneously for a long period of time, so they prioritized the most-used extensions first and will enable more extensions as the APIs are hooked back up underneath.
This had tangible benefits - the new browser is significantly snappier and uses less power in my experience.
>We should take firefox out of their hands before it is too late.
It's open source, if you aren't satisfied with the speed of their progress, you can always help out. You say you'd like to take this work out of their hands? Well, here it is.
These are, specifically, unimplemented APIs and known API bugs in the new Firefox Mobile, that are on the Mozilla TODO list, and for which contributions would presumably be welcome. Enjoy.
Unless when you said "we", you actually meant "other people".
I have for example one small extension that I maintain, which is basically little more than a glorified page script which therefore doesn't use any special extension APIs at all. Despite that, it took months for it to be enabled, and if it wasn't as popular as it is I might still be waiting even today.
> the new browser is significantly snappier and uses less power in my experience.
Ha! From a cold start, on my phone launching the new Firefox (with less add-ons) and loading a page seems to take approximatively twice as long as on Firefox 68, and still ~50 % more than even on Firefox 55.
So on the one hand fixing that bug makes sense and has some value, but on the other hand and in practice the increased startup time still feels rather quite annoying, too, given that my phone isn't the latest and fastest model.
*this have nothing to do with my comment*
I am talking two or three iterations AFTER that. please, stop commenting long posts where you have no idea.
yes, mozilla moved to a new engine. Before that they moved to a new extension format. etc etc etc.
All the extension developers worked on the ports already, *THEN* mozilla, only for mobile, enabled "recommended extensions" which was fine. Until they DISABLED the non-recommended (not non-updated to the new tech).
It have nothing to do with technology. In fact I have many of those extensions working on my phone by fiddling with their whitelist urls. No problem running them AT ALL.
This is political.
We've been waiting nearly a year and a half so far for them to enable extensions on the new engine.
One needs to make a mozilla account to complete the last steps and that's where I've been holding off. Mostly out of laziness and also from lack of necessity since I just moved on to other browsers in the mean time.