2 ms·
> Simple, they switched to the webextension API a few years ago as it makes development of extension across browsers much easier. Great idea to prioritize inte
by pessimizer 4y ago
> Simple, they switched to the webextension API a few years ago as it makes development of extension across browsers much easier.
Great idea to prioritize interop when the people who you're trying to interop with are gulping large chunks of your userbase. Very important to make sure that Firefox had parity with Chrome in extensions, the only area where Firefox previously had a massive advantage over Chrome.
- creesch 4y ago> the only area where Firefox previously had a massive advantage over Chrome. It didn't though, because the API was different a lot of extensions that appeal to a broader user base were not made available on firefox (anymore). Yes, the previous framework did allow other use cases more suitable for power users but those are a fraction of the total user base. And in general it hugely simplified extension development. Instead of having to maintain various code paths for different browsers and accounting for slightly incompatible APIs this was no longer needed.