3 ms·
Speaking solely as a web developer: good riddance, the pre-KitKat stock Android browser is a piece of shit. It relies on an old fork of Webkit that has none of
by nostrademons 13y ago
Speaking solely as a web developer: good riddance, the pre-KitKat stock Android browser is a piece of shit. It relies on an old fork of Webkit that has none of the features of the modern web, no GPU support, and a lot of outright bugs (like it would flip back to the first frame of a CSS3 animation right before the animation completes, creating an ugly flicker).
Without this change we'd be left with Android Browser & clones as the IE6 of the mobile web. I'm hoping all the OEMs build their own browsers off the Chromium WebView that ships in KitKat; then at least we only have to worry about Chromium and Mobile Safari.
- icebraining 13y agoHey, some of us use Firefox.
- nostrademons 13y ago...which at least follows web standards fairly closely. Firefox is nearly as quick as Chrome at keeping up with the latest and greatest. Android Browser hasn't been updated in years.
- cpeterso 13y agoPlus, Firefox still supports Froyo and Gingerbread. Chrome only supports Ice Cream Sandwich and later. Android users with older phones have been abandoned by Google, but at least they can download a modern web browser.
- fidotron 13y agoBut speaking as an Android user, Android Chrome is a slow piece of crap, (with that horrible text resizing thing going on) while the stock browser actually works.
- nostrademons 13y agoI've been using Android Chrome as a user since it was in beta; it's been my default browser for at least a year now. I had far more problems with Android Browser than Android Chrome. (They are working on speed though; not much attention has been paid to performance optimizations besides using the GPU for animations.)
- kllrnohj 13y ago> It relies on an old fork of Webkit that has none of the features of the modern web, no GPU support, and a lot of outright bugs That's really not true. It's an old version of Webkit NOW, yes, but it wasn't when it was still being updated all the way up to Android 4.0. And it absolutely has GPU support - it's had GPU accelerated compositing for CSS 3D transforms, fixed position elements, and scrollable divs since 3.0. It had all that before Chrome did. In fact Chrome's GPU & rendering architecture today matches what Android Browser has had since 4.1. Chrome had to catch up to Android Browser in many respects. > I'm hoping all the OEMs build their own browsers off the Chromium WebView that ships in KitKat Chromium WebView is a requirement. Unless OEMs decide to start maintaining their own webkit forks (something they have not done so far), there will be nothing else but Chromium on Android from 4.4 onwards.