Cannot reply to your question but there are more firefox versions and forks that support pull to refresh:
Thank you for the heads up, I didn't see this when I tried FF beta, maybe I need to look again lol.
But honestly what is the difference between beta and nightly? Is nightly unstable for daily basis? Because I haven't found any bugs in the wild.
And IceRaven
Damn, I must have overlooked that because I have it installed and it is not working.
See this bug that's been open for very long. At the bottom someone has a solution that may work. https://bugzilla.mozilla.org/show_bug.cgi?id=1807364
Using Beta 114, I confirmed that setting dom.ipc.processPrelaunch.lowmem_mb to 0 MB fixes this issue which seems to happen when there's a memory pressure in the system
I’m using Firefox Nightly, because I think it is the only version that has a working pull to refresh.
Firefox Beta for Android has pull to refresh that works.
Really? Does it need to be activated? I tried it and it didn't work a few days ago.
.
I actually disabled it, but it does work.
lol, definitely overlooked it then, thanks for the heads up!
Although I'm struggling to see the differences in all these FF clients.
You mean you want to avoid FF flushing your tabs?
Um, I don't know if stock FF has that, but in IceRaven there's an option for the exact opposite - to flush the content of tabs so that when the browser is minimised, Android is less likely to kill it outright. I assume it's just some config option being exposed as a menu item.
But note the meaning of the feature - if your tabs stay active, they take up resources and so it's more likely Android will kill the entire browser process.
IR also has pull to refresh btw, as do other forks.
You mean you want to avoid FF flushing your tabs?
Yeah well not permanently, as I recently moved from Chrome I think Chrome holds them on the RAM a longer time, so you can be multitasking within the browser and other apps.
I don't understand why IceRaven would do that, why kill the tabs to have a browser without content running in the background?
But if it is an option as you said, maaaaybe that is what I saw here on the wild 🤷🏻
why kill the tabs to have a browser without content running in the background?
It doesn't kill the tabs, just removes their content from active memory.
If you have private tabs open and the fucking OS kills the browser, then those tabs are gone and you need to reopen them from scratch, log in again etc. With this option enabled, the browser can free up more memory so the OS is less likely to kill the browser.
Now, with some phone brands it might not matter as their background process culling is more aggressive, but with default Android there's a difference.
But it's just an option, idk if it's disabled by default. Maybe there's an extra config option for it somewhere.
Yea FF on Android does take up more memory than Chromium, maybe because Chromium can share more Android core things, idk. Either way, if you run out of memory, the browser will start flushing things regardless, so it doesn't crash.
Chromium also does a different thing where it still shows the unloaded website but in "preview" mode and you need to refresh it anyway, which I find even more annoying.
A place to discuss the news and latest developments on the open-source browser Firefox