3 ms·
> Chrome is the mobile browser that is built for web > applications and sadly Firefox Mobile is not. And > actually this has always been a difference in
by kibwen 11y ago
> Chrome is the mobile browser that is built for web
> applications and sadly Firefox Mobile is not. And
> actually this has always been a difference in
> philosophy. It's why Chrome started with the one
> process per tab and with strong sandboxing on the
> desktop as well, Chrome being built for applications.
Looking forward, Mozilla is adopting this philosophy in Servo by targeting mobile first and foremost, as well as taking sandboxing seriously from the get-go: https://twitter.com/pcwalton/status/667494515582758913 https://twitter.com/pcwalton/status/667494515582758913
- mtgx 11y ago> taking sandboxing seriously from the get-go I'm curious how that would work. I know the desktop Firefox will only - very gradually - move to a complete sandboxing architecture, because of the way it will break many add-ons. But Firefox for Android already supports extensions - is it only the Chrome-like/WebExtensions-like extensions it supports now? Is that why it will be easier to move to a complete sandboxing system on mobile first?
- Gankro 11y agoMulti-process to isolate tasks, and whitelists for system apis to minimize the priviledge of each task. Servo has no back-compat concerns. It will be using browser.html -- no legacy XUL addons at all.