I am having problems installing on macOS Catalina bets. Same as installing Chrome.
Firefox 68.0
191–200 of 282 posts
Re: Firefox 68.0
#192Earlier quoted context omitted.
If there was a viable competitor, I would consider using it. There isn't.
There is. You just don't want to spend the money or use the phones/tablets from said competitor.
iOS doesn't allow anywhere near the level of customization that Android does, nor does it allow 3rd party browser engines at all, however there's Sailfish OS and maybe the Librem 5 soon.
Re: Firefox 68.0
#193Earlier 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…
>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. Speaking as an end-user, I find the eagerness with which web developers re-purpose key events to be extremely aggravating. If I hit ctrl-F, I want to use Firefox's native full page text search, not jump to the in-site search box. I'd like to see M…
We have a thing in Tridactyl for this, actually ("blacklistkeys" if you're a user).
You roll your own by writing a userscript (e.g. Tampermonkey) that adds an event listener to keydown which runs key.cancelBubble = true and key.stopPropagation(). See line 343 https://github.com/tridactyl/tridactyl/blob/master/src/conte... (starts "leavegithubalone").
Re: Firefox 68.0
#194Earlier 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…
> However, we do have concrete plans for supporting adblocking as a built-in feature in the near future
reading this almost makes me cry because that is the same bullshit google is telling us with chrome.
Firefox is not supposed to block ads! Firefox only has to provide an interface for addons so they can do whatever(!!!) they want (for example blocking ads or installing malware on your system).
Please don't sacrifice our freedom for a wrong understanding of security (like that addon-signing you pulled lately).
Re: Firefox 68.0
#195This 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…
"Fenix MVP will not replace Fennec" (MVP meaning "Minimum Viable Product"). https://github.com/mozilla-mobile/fenix/issues/662#issuecomm... I'm sure Fennec users will not be migrated to Fenix until extensions are supported. This would be a big fuck up and Mozilla is aware of this. Linked bugs about the user agent seem irrelevant to this issue. Everything will be okay. You can sleep on both ears.
Sorry but this seems conflicting with what callahad replied above
https://news.ycombinator.com/item?id=20394503 when answering "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 only as a stopgap.
> More fundamentally, when considering major features like add-on support, we want to take the time to ensure that we're getting our design right at all relevant levels: Firefox Preview, the underlying GeckoView library, and the Gecko engine itself. And though development on Preview moves quickly, there's still a lot of design and development work yet to be done.
My understanding is that there's a good chance that Firefox 68, which supports extensions, will reach EOL before 69+ gets support for extensions.
Re: Firefox 68.0
#196Wish there was a log in Firefox to determine how/why uBlock Origin keeps getting uninstalled across all my machines which are synced with my Firefox account.
Sync does have a log. Maybe that would help?
https://wiki.mozilla.org/CloudServices/Sync/File_a_desktop_b...
Re: Firefox 68.0
#197Earlier quoted context omitted.
Did they "break" - ie some bug caused a problem - or did they change the framework add-ons used after giving months of notice? Most users use no add-ons, and wouldn't notice the change, and many of those who do were aware of this ahead of time even if the add-on developers were slow to wake up to the reality.
> Most users use no add-ons Do you have the data for this? I know I live in a techie bubble, but it sure doesn't fit with my experience or the experiences of others I know who talk about it.
Firefox Public Data Report:
https://data.firefox.com/dashboard/usage-behavior
"Has Add-on" has been between 33-38% for the last two years.
Re: Firefox 68.0
#198Earlier quoted context omitted.
You do you [1] [1] https://github.com/kiwibrowser
This is just for show. [1] >No. The browser is not fully open source like open in open source. It is a common myth and misconception about Kiwi Browser. >Damn, 1 commit and nothing else but keeps updating and releasing apks? Looked into the issues and scarcely seen replies. >I think this repo is just to show that "hey, I provided the so-called source code (even though not fully open-source as said above) so trust me…
The way you share quotes sounds like you personally have a problem with the browser :D
Kiwi was started as a fun+independent project, then more and more people asked access to some source to be able to develop their own hacks (new tab page, extensions, bottom toolbar, import/export bookmarks, AMP, etc) and they are shared when the devs ask politely.
At the end of the day, if you use Samsung, Kiwi, Fennec or Yandex, what matters is to understand why the developers are doing their project, what do they get from it (not necessarily money), and what are the influences around. The source-code is one indicator, and, unless you actually have reproducible builds (and only Fennec has them from all the mentioned browsers) you have to use your intuition.
Re: Firefox 68.0
#199Earlier quoted context omitted.
> Well, no. I don't want to use a browser that is developed by an advertising company ... on an operating system developed by the exact same advertising company?
LineageOS[1] exists, and it may as well be a non-GNU mobile distribution of Linux with support for Android apps like Firefox. [1] https://lineageos.org/
I've given up on custom ROMs. There's always only an extremely limited set of devices that are supported, and those devices are EOL rather too quickly, forcing us to use custom builds from someone not directly affiliated with the project.
To be clear, not one of the Android devices I've purchased have ever had official support. I'm using a Samsung a8 at the moment.
I hope the custom rom community finds a better mechanism for providing better device coverage.
Re: Firefox 68.0
#200This 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…
Hi. I work for Mozilla. Firefox for Android is not dead. You are free to continue using it. It will continue to support add-ons, and it will receive regular security updates and bugfixes for at least the next year. We are focusing all new feature development in Firefox Preview, but we're continuing to support Firefox for Android as an Extended Support Release while we build Preview. And, for what it's worth, we do un…
That's a shame I used to quite like Firefox on my mobile. I guess this is back to Chrome soon then :(