3 ms·
Have you tried Firefox Browser (Nightly for Developers)? I'm using that on Android since the whole debacle that you described. It mostly works fine and from the
by climb_stealth 5y ago
Have you tried Firefox Browser (Nightly for Developers)? I'm using that on Android since the whole debacle that you described. It mostly works fine and from the start it already had a lot of the features that are missing in the main Firefox. I don't understand how it can all be working fine in the dev build whilst the main visible product is so lacking. Sometimes the UI gets some odd changes with updates, but I haven't had to switch browsers again so far. Though I'm not sure if your specific issues are addressed. I mostly ignore or work around them. I have pull to refresh disabled for example as it was driving me nuts.
And yes, I can't understand how Firefox was updated with so many features missing and it is still not there. It's quite sad, really.
- nonbirithm 5y agoI am running Nightly, actually, mostly in the hopes that the most important issues get fixed sooner. It doesn't seem like that's happening. I might end up going back to stable pretty soon. I should also mention that Chrome on Android has none of the issues I described earlier. Wouldn't it make sense that even someone like me that desperately wants a reason to stand with Mozilla ends up giving into temptation and uses Brave half the time? I hope that Mozilla can learn from its mistakes and stay competitive, given that the alternative is an Android browser monoculture. They're one of the few organizations with the resources to implement the increasingly encroaching burden of new web specifications, and I don't think a community-supported fork of Firefox or FfA will survive without some kind of miracle (see Waterfox and its need to eventually implement Web Components or fall out of relevance). The partial WebExtension support on mobile alone is one thing that gives me hope FfA will continue to see support for the near future.