Apple made a decision at some point (seemingly under pressure) to allow not just Chrome, but all "browsers" (a term that I feel needs to be put in quotes, as all of these applications, including Chrome, must use Apple's HTML renderer, and only thereby have control over some aspects of how requests are cached and the surrounding UI).
Yes: that was actually what I was intending to imply; specifically, that Google wasn't blazing trails here nor are they being given special exceptions.
Opera Mini is not a browser but rather a view into a browser in The Cloud. All network connections and JavaScript evaluation happens elsewhere, and the phone displays the resulting image and proxies clicks back to the server. Apple's sticking point has always been code evaluation on the phone, and currently only permits JavaScriptCore to evaluate code retrieved over the network.
Comments
Apple made a decision at some point (seemingly under pressure) to allow not just Chrome, but all "browsers" (a term that I feel needs to be put in quotes, as all of these applications, including Chrome, must use Apple's HTML renderer, and only thereby have control over some aspects of how requests are cached and the surrounding UI).
Hasn't Apple allowed browser apps that wrap UIWebKit well before Chrome?
I'm pretty sure there were already stand-alone browser apps in the App Store before Chrome came.
Yes: that was actually what I was intending to imply; specifically, that Google wasn't blazing trails here nor are they being given special exceptions.
There were for sure. Opera is one.
Opera Mini is not a browser but rather a view into a browser in The Cloud. All network connections and JavaScript evaluation happens elsewhere, and the phone displays the resulting image and proxies clicks back to the server. Apple's sticking point has always been code evaluation on the phone, and currently only permits JavaScriptCore to evaluate code retrieved over the network.