Link to the AppStore http://itunes.apple.com/uk/app/opera-mini-web-browser/id3637... — It's not as fast as I expected, but still For now: "un-zommed" content is unreadable, for instance, nytimes.com in Opera http://cl.ly/JIP vs Safari Mobile: http://cl.ly/J9i (which is also unreadable, but well, I can distinct letters)
Does the Opera browser app itself not interpret javascript? Is it offloaded to the iPhone's WebKit/rendering engine? Otherwise this would seem to fly in the face of the recent change to 3.3.1.
Think of Opera Mini as an interactive image viewer. They interpret all JavaScript on the server side and sent result back to the client using OBML[1]. Or at least that's how it works on other device.
Link to the AppStore http://itunes.apple.com/uk/app/opera-mini-web-browser/id3637... — It's not as fast as I expected, but still For now: "un-zommed" content is unreadable, for instance, nytimes.com in Opera http://cl.ly/JIP vs Safari Mobile: http://cl.ly/J9i (which is also unreadable, but well, I can distinct letters)
Does the Opera browser app itself not interpret javascript? Is it offloaded to the iPhone's WebKit/rendering engine? Otherwise this would seem to fly in the face of the recent change to 3.3.1.
The app is Opera Mini, not Opera Mobile, so no, it does not. Opera Mini is a proxy browser: all the heavy lifting, including JavaScript and most rendering, happens on one of Opera's proxy servers. The Opera Mini app receives a heavily pre-processed and compressed version of the webpage, in some custom data format. The app itself only does rendering, not processing or interpreting.
Does the Opera browser app itself not interpret javascript? Is it offloaded to the iPhone's WebKit/rendering engine? Otherwise this would seem to fly in the face of the recent change to 3.3.1.
No, the Opera app does not run JavaScript itself. The app communicates to Opera's server, and it's the server that does HTTP with the website, runs the JavaScript, and compresses the HTML and sends it down to the app.
The restriction on downloading and executing code has been in the developer agreement since the beginning. It's not a recent thing.
Does the Opera browser app itself not interpret javascript? Is it offloaded to the iPhone's WebKit/rendering engine? Otherwise this would seem to fly in the face of the recent change to 3.3.1.
Think of Opera Mini as an interactive image viewer. They interpret all JavaScript on the server side and sent result back to the client using OBML[1]. Or at least that's how it works on other device. [1] http://en.wikipedia.org/wiki/Opera_Mini#Functionality
Interesting. The section on JavaScript support is not encouraging actually. Can anyone report on attempting to use a js-heavy web-app through Opera Mini, e.g. Gmail?