Earlier quoted context omitted.
Will Preview be guaranteed to support extensions before Firefox for Android goes EOL?
I can't make any specific commitment, but there's a lot of time between now and Firefox for Android going EOL (and we haven't committed to specific timing for that, either.) However, we do have concrete plans for supporting adblocking as a built-in feature in the near future ( https://github.com/mozilla-mobile/fenix/issues/96 ), which should make Preview more palatable to folks who rely on add-ons for that, even if o…
Firefox 68.0
171–180 of 282 posts
Re: Firefox 68.0
#172Earlier quoted context omitted.
FWIW, there are quite a few things that haven't been added to the API, most importantly the ability to accept key events from pages where our content script isn't running. In fact, very little has been added that has made our life easier (the main one being the search API) since we first started developing Tridactyl. Features have actually been taken away from us - notably the ability to operate on PDFs. Not to detra…
Thanks for the update. It's been a long time since I've seen this brought up here.
Re: Firefox 68.0
#173> Local files can no longer access other files in the same directory. What impact will this have on web development without a web server? It sounds like you won't be able to load CSS or JS.
Worse comes to worst it’ll be a toggleable flag, but it is still annoying.
Re: Firefox 68.0
#174This marks the last Android release with extensions/add-on support. There will not be a 69 release of this edition of Firefox for Android ("Fennec"). The new remake of the mobile browser ("Fenix") does not have extensions support and it is on an indefinite and easily ignorable backlog. It is explicitly not being worked on this quarter. At the end of this quarter is the scheduled release of Firefox 69. Unless there's…
Re: Firefox 68.0
#175Earlier quoted context omitted.
> This reads like FUD to me. The dev team know how important extensions are to their users. Just because they know how important it is doesn't mean they care . I'm sure Google also knew how important ad blocking was to many Chrome users when they decided to remove that functionality from their browser, too.
uBlock seems to work just fine, not sure why you're claiming they removed it.
Re: Firefox 68.0
#176Earlier quoted context omitted.
Wait what? Extensions are the biggest reason I'm using Firefox on my mobile and the only way I got people to switch to it. How can they just be removing them for any period of time?
Extensions is the ONLY reason to use Firefox on Android. It's not good browser compared to Chrome on slower Android phones, apart from being customizable. To me it's even the single biggest reason to use Android over iOS as there's no full featured browser on iOS.
Re: Firefox 68.0
#177Earlier quoted context omitted.
This is a lot of FUD. Making a browser is hard, and making a modular browser is harder. It's clearly on their list of things to do, but it's behind all the other "making a browser" things.
They've made no commitment to extensions, but clearly are targeting this new replacement browser for version 69 in a few months. What they haven't done is given a clear statement. Nothing about if their replacement is going to drop extension support. But every response from Mozilla has been a sidestep and that I cannot overlook.
That is incorrect, and stems from a misunderstanding of our release model.
> What they haven't done is given a clear statement.
The clearest statement is this dev-platform post from April, https://groups.google.com/forum/#!topic/mozilla.dev.platform..., which includes a link to a much more detailed project planning document.
> Nothing about if their replacement is going to drop extension support.
That's because we are not yet ready to make public commitments. Honest. We're building the app and its underlying embedding library (GeckoView) from scratch, and as with all new greenfield projects, we're still working on getting the foundation right. It's simply too early to forecast how that specific design and development work will play out.
Re: Firefox 68.0
#178This marks the last Android release with extensions/add-on support. There will not be a 69 release of this edition of Firefox for Android ("Fennec"). The new remake of the mobile browser ("Fenix") does not have extensions support and it is on an indefinite and easily ignorable backlog. It is explicitly not being worked on this quarter. At the end of this quarter is the scheduled release of Firefox 69. Unless there's…
Without uBlock Origin on mobile Firefox, I guess I'll just stop visiting websites on mobile devices entirely. They're unusable without ad blocking.
Re: Firefox 68.0
#179Re: Firefox 68.0
#180Not sure if placebo but firefox nightly 70 is a looot more snappier than 69. Now I regret chrome almost not at all. Thanks for the hard work to all involved.
That's placebo -- Nightly is built from our trunk. The only thing that changes between Nightly 69 and Nightly 70 is a version bump.
Or maybe it's a different rendering library / os / gpu driver interaction.