Fenix VS bromite

Firefox on Android to this day does not switch to dark mode automatically

https://github.com/mozilla-mobile/fenix/issues/27568

https://bugzilla.mozilla.org/show_bug.cgi?id=1813529

They're probably mixing the desktop and mobile application up. Its access was disabled in official builds (but forks and custom builds such as some on F-Droid still have it)

https://github.com/mozilla-mobile/fenix/issues/21276

It's been that way for years: https://github.com/mozilla-mobile/fenix/issues/20351

I lost hope it and other issues would be fixed and moved to Chromium on Android.

Firefox for Android was rewritten pretty much from scratch circa 2020. Collections are one of its many unfinished and poorly-thought-out features, and they never got around to implementing the ability to sync Collections to desktop. It was a known problem in 2019, while the rewrite was being worked on, and Mozilla doesn't appear to have given it any attention in the years since.

People have been asking for this for over a year via Mozilla's current feedback channels, and for two years on the previous issue-reporting venue, to no avail. It was automatically moved from the old venue to Bugzilla ostensibly because Bugzilla makes it easier to track and work on issue reports, but they haven't actually worked on that issue report at all.

Known issue, not a new issue, and unlikely to be fixed any time soon, unfortunately. I had this before I stopped using the Android version a year ago. It was reported as a bug at least a year ago on their old issue tracker, and later moved to the current one, where last activity on the issue report was three months ago. No apparent progress toward any fix.

Since Fenix's first release they've been saying that the absurd limitations on add-ons support were only temporary, and they would have quickly increased the number of supported ones.

And instead absolutely nothing changed for three years.

Furthermore the insane bugs from which Fenix suffers from its release (https://github.com/mozilla-mobile/fenix/issues/12731) (making it unbearable) have been left hanging, focusing the few resources on dumb ui experiments.

So everything suggested that Mozilla did not care of its Android browser, or actually that they were deliberately sabotaging it.

This news instead represents a huge improvement, hence my bewilderment.

I don't know what people who downvoted my message thought I meant.

https://github.com/mozilla-mobile/fenix/issues/20012 and https://bugzilla.mozilla.org/show_bug.cgi?id=101865

Our goal with the Chromium provided in CalyxOS has been to provide a browser with a solid base of privacy and security enhancements vs Chromium (and by extension, vs Chrome) while still allowing most sites and WebView-based apps to function as expected out of the box. We do this by using select changes from Cromite (and prior to that, Bromite). Some of these include the under-the-hood deactivation of intrusive features and analytics, while others provide additional site settings to adjust features like WebGL and WebRTC, features which are sometimes necessary but which can aid in fingerprinting or identification when turned on. We also bring in the legacy ad blocker from Bromite/Cromite to offer some reasonable protection from the worst kinds of ads. You can find and adjust these features in Settings.

https://github.com/bromite/bromite Browser (based on Chrome)

Normally, I'd recommend Bromite as a lightweight Chromium-based browser with built-in adblocking, but the project appears to be asleep right now. It might be worth checking it in a few weeks, though.

Bromite via either its site/Fdroid, GitHub or Woolyss site has a bottom bar available in accessibility settings. (The first one has been unmaintained for a while, but has auto updates available if they ever drop. The other two are up to date but must be updated manually.)

Bromite hasn't been updated since December: https://github.com/bromite/bromite/releases

context: https://github.com/bromite/bromite/issues/2141