Comment

Comment by dralley

>They disabled many loved extensions by power users for absolutely no reason at all!

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.

https://mzl.la/3jgCsW3

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".

parent dralley 5 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton