3 ms·
Just be mindful that Firefox/Android doesn't have process isolation. https://www.privacyguides.org/mobile-browsers/#android https://www.privacyguides.org/mobile
by dngray 4y ago
Just be mindful that Firefox/Android doesn't have process isolation. https://www.privacyguides.org/mobile-browsers/#android https://www.privacyguides.org/mobile-browsers/#android
This is because the desktop browser uses the full "Gecko" renderer, but mobile uses "GeckoView", that doesn't have that implemented yet.
- iggldiggl 4y agoGeckoView is literally Gecko with an Android API wrapped around it, so that sentence doesn't really explain anything. The actual thing is that simply each app embedding Gecko needs to be brought up to speed separately, and if Android is lagging behind, it just is, "GeckoView" or not. (Even before the invention of GeckoView, due to understaffing Android Firefox used to lag behind in terms of multi-process capability, so nothing new under the sun…)