Would have to wait until next ESR:
users can expect Tor Browser Stable 16.0 (based on Firefox ESR 153) to be released about halfway through Q3 of 2026
can an Android browser dev (@celenity?) comment on what this actually entails. Does this bridge the gap between IronFox and Chromium-based browsers on Android? I’ve read the articles linked from docs/Limitations.md · dev · IronFox OSS / IronFox · GitLab and it suggests that Firefox’s sandboxing/fission is still nowhere near the level of Chromium. Is IronFox going to updates its limitations/FAQ if these features are a big deal?
Well, I asked him on Mastodon about IronFox not enabling this by default and this was the answer
“well, we currently don’t enable those by default due to us finding them to still unfortunately be too experimental/buggy in testing
but we’re keeping an eye on them and hope to enable them by default in the near future. for now, we at least allow users to enable them manually if desired from secret settings (and afaik we’re the first/maybe only? gecko browser to support enabling them at all, because we also enable support for it at build-time when building gecko/geckoview)
so you’re welcome to enable them, and if they work for you/don’t cause issues, you can keep them on (if you do decide to enable them, please lmk how your experience is! we def need feedback on it).”
7 Likes
About the comparison about chromium and gecko, idk about it. Maybe he (@celenity) can answer more properly.
Release 147.0 is out today, and Fission should indeed be enabled by default, per the release notes.
Have yet to get the update to see for myself, can anyone confirm?
4 Likes
I don’t have regular Firefox on Android. The code that checks for beta on android was removed.
1 Like
Opening about:support with Firefox for Android, version 147.0.1:
- Fission Windows: “Enabled by default”
- Remote Processes -> Isolated Web Content: “1” (Probably means enabled.)
6 Likes