5 ms·
Not so much because we're fed up with it as simply the performance characteristics of low end Android phones and the user expectations regarding mobile browsers
by gcp 12y ago
Not so much because we're fed up with it as simply the performance characteristics of low end Android phones and the user expectations regarding mobile browsers not being compatible.
Startup time is just so darn important.
Not being able to rely on Gecko for stuff that must be accessible immediately means that Firefox for Android has to re-implement a load of things. That's not a choice that was made voluntarily.
- sp332 12y agoDoesn't it still use Gecko though?
- azakai 12y agoYes, for web content, but not to render all of the UI as well.
- deleted 12y ago[deleted]
- csuwldcat 12y agoYes, Firefox for Android still uses Gecko.
- keeperofdakeys 12y agoKeep in mind that on the desktop, firefox renders the user interface using XUL and CSS. In this case, (I assume) it's just using a native android ui instead.
- JohnTHaller 12y agoOn the plus side, Firefox for Android loads up quite a lot faster relative to the built-in Browser and Chrome today than it used to in the XUL days.