What I like most about firefox is the mobile version supports addons like ublock origin. In mobile Chrome the support for add blockers is not really well supported.
Using ghostery to block ads and tracking is shooting oneself and everybody else in the foot (feet?).
There are some addons which try to emulate text reflow on tap, but it's pain to use at best.
Reader mode is a workaround, text reflow is the solution. It a reason to use Opera on Android. I wonder if it's so hard to implement that nobody else coded it.
Unfortunately the about:config setting for text reflow in one of the last comnents is not in Firefox anymore.
Ironically that page is an example of a page where reader mode doesn't work.
Is this just not a default setting? An add-on I can get? Or just not something you can do?
So worst case scenario is:
1. Wake the screen.
2. Unlock phone.
3. reopen Firefox, because I've checked texts/email/social feed whatever after starting the music.
4. find the tab playing music.
5. Navigate to whatever in that tab controls the audio .
6. pause it.
Also, I also found that feature to be not very reliable since Android 6, which quite aggressively puts background apps to sleep (at least on my phone with "only" 2GB of RAM). I find that any extensive use outside Firefox will make the background playing stop rather quickly.
It annoys me every day that I can't put on a Youtube video and then continue listening to it while I do something else with my iPhone afaict.
If I didn't want that, I would pause it first.
That's a bit harsh.
> It's a non-Firefox browser just set up to sync FF settings and bookmarks and kinda look like Firefox.
It's a WebView-wrapper like all other iOS "browsers" because that's everything Apple will allow. To be fair though, synced data, history, passwords and settings is probably one of the most important things for a mobile user, where entering things manually is a pain in the ass.
Basically NOT having this would risk losing users on the desktop (to something which does sync). And right now, Firefox can't afford to do that.
Which in turn would mean that lots of people would have to shell out several hundred dollars more for a Mac just to build it.
It's not exactly a stellar deployment-model when you try to push it at scale.
Separately from the ban on third-party browsing engines, iOS has technical restrictions preventing you from mapping unsigned code as executable, so JITs don't work. There may be some ways around that if you have a developer signature, but its messy at minimum.
We can only blame Apple for that though, and not Mozilla for a lack of trying.
I was extremely surprised and disappointed (to say the least) when I moved to iOS and found this missing.