The iOS version of Chrome doesn't use Chrome's rendering and JavaScript engines though, per the App Store rules it has to use WebKit [0]. So, any other browser app on iOS would have the same problems as mobile Safari.
Not quite my area of expertise, but I believe that browsers on Android also tend to use the core Android browser components though they can dress them up slightly differently.
> ...I believe that browsers on Android also tend to use...
The word 'also' doesn't belong here. Browsers on iOS don't tend to use core iOS components (WebView) : they are forced to. Your statement really isn't a counter point.
Browsers on Android are not required to use Android's built in WebViews. And several alternative browser engines are offered by the platform[0].
Android has no specific restrictions in place. Although it is the path of least resistance to use the built in WebView, since you now don't need to deploy your own.
[0] Including: Blink (Amazon Silk, Chrome, Opera), WebKit (BlackBerry, Dolphin, et al), Gecko (Firefox, Minimo), NetFront (Blazer). At the moment WebKit derivatives seem to be most popular, but several browsers re-build it from the source rather than just using Android's WebKit components.
Yea, I just really like that I can access all of my open tabs with it. It also context switches better with iOS outlook if you click on links you can quickly go back to outlook.
On iOS, all 3rd-party browsers (and even the upcoming Firefox for iOS) are using the rendering engine of Safari. The complaint is not about Safari the browser but more about its rendering engine.
