Earlier quoted context omitted.
The really galling thing is they lied right to our damn faces about how "the new faster systems breaks the old add-on system" while they were still using XUL behind the scenes. In fact an HN reader compiled versions of Firefox 57 and above with user-installed XUL enabled and they work perfectly well.
Nothing is really stopping people from keeping those extensions compatible. Unsupported doesn't mean impossible - it just means you need to do some tweaks: https://webextensions-experiments.readthedocs.io
Add-on support in new Firefox for Android (2021)
81–90 of 220 posts
Re: Add-on support in new Firefox for Android (2021)
#82Earlier quoted context omitted.
This pretty much feels to me what is happening to Mozilla as an organization from an outsider perspective. Engineering is no longer as important as the evangelism and management is making strange decisions that lack focus on what the target audience really is.
Quoted post unavailable.
Re: Add-on support in new Firefox for Android (2021)
#83Fenix is basically a whole new browser, and that means that all features need to be implemented again (which takes a lot of time, and I don't think Firefox developers have much of it). Lots of Fennec features are still missing (view source code, save as pdf, install general addons, the whole about:config...). Why they changed is a mystery, maybe the old browser had a core privacy bug or something that couldn't be fix…
The web (HTML/CSS/JS/JIT/WebAssembly/Audio/WebGL/WebRTC/etc) engine is exactly the same, the rendering engine (WebRender) is the same, synchronization is the same.
The UI is completely new - that's it.
This is not a wholly new browser, this is a wholly new UI.
Re: Add-on support in new Firefox for Android (2021)
#84Earlier quoted context omitted.
Nothing is really stopping people from keeping those extensions compatible. Unsupported doesn't mean impossible - it just means you need to do some tweaks: https://webextensions-experiments.readthedocs.io
I'm not understanding how that relates to the fact that the only thing stopping users from installing their XUL extensions on FF57 was a software switch they weren't allowed to touch without editing and compiling from source.
Re: Add-on support in new Firefox for Android (2021)
#85Earlier quoted context omitted.
"the whitelist has a purpose" doesn't really capture what's going on, though. It's more like they whitelisted some of the most popular extensions and then just stopped completely with no intention of continuing. With the much more limited plugin API (and simple html plug-in config pages) of the new browsers you'd think it would be easier to build and vet secure, cross platform add-ons.
Somewhere in a parallel universe, Mozilla just let all the plugins claim compatability, and vaguely fascist users who dont like their politics are complaining that the instability of Mozilla on Android is the reason they hate them. And further along, in a universe where they poured a lot of time energy and money into fixing the whole plugin ecosystem and succeeded, they're complaining about something that didn't get…
Do they have any desire to just.. make a good browser that fulfills peoples needs?
Re: Add-on support in new Firefox for Android (2021)
#86(Former Mozilla developer here, who worked on GeckoView[1], the modern way to embed Gecko into Android apps, including all currently shipped Mozilla browsers on Android) From an engineering perspective, the sad thing about this is that the work to finish extensions in GeckoView was essentially completed in the months after the initial Fenix release. When GeckoView was still being rolled out into release, we understan…
Can you elaborate how engineering on an open source product is prevented from doing the right thing™ by management?
Re: Add-on support in new Firefox for Android (2021)
#87Earlier quoted context omitted.
This pretty much feels to me what is happening to Mozilla as an organization from an outsider perspective. Engineering is no longer as important as the evangelism and management is making strange decisions that lack focus on what the target audience really is.
Quoted post unavailable.
Re: Add-on support in new Firefox for Android (2021)
#88Re: Add-on support in new Firefox for Android (2021)
#89I like using Firefox on Android because uBlock origin makes mobile browsing at least tolerable and it lets me use the "desktop mode" view on certain sites so e.g. I can listen to youtube playlists even if the phone is locked without paying for a premium service (for what I consider basic functionality). Surprised to hear literally the sole reason I use it on mobile is also neglected. Do they think they're going to ou…
NewPipe on F-Droid is a killer app.
Re: Add-on support in new Firefox for Android (2021)
#90Earlier quoted context omitted.
"the whitelist has a purpose" doesn't really capture what's going on, though. It's more like they whitelisted some of the most popular extensions and then just stopped completely with no intention of continuing. With the much more limited plugin API (and simple html plug-in config pages) of the new browsers you'd think it would be easier to build and vet secure, cross platform add-ons.
Somewhere in a parallel universe, Mozilla just let all the plugins claim compatability, and vaguely fascist users who dont like their politics are complaining that the instability of Mozilla on Android is the reason they hate them. And further along, in a universe where they poured a lot of time energy and money into fixing the whole plugin ecosystem and succeeded, they're complaining about something that didn't get…
I've seen this one before, a GNOME apologist insinuating that anybody who wants thumbnails in the GTK filepicker is probably a 4chan user. Is this the new trendy way to dismiss criticism of software? Insinuate that anybody making specific concrete complaints about software has invalid political beliefs completely tangential to the feature/bug being criticized? What fun!