Nope — Opera Mobile somehow had the same problem. I got through editing my post using the phone keypad (actually, due to T9, not as painful as it sounds) but when I was all done and published the post, it turned up empty — everything I had painfully thumbed in had been lost. Gah!
Filed by Daniel Appelquist at 14:10 under Mobile Web
I'm an American Ex-Pat living in London. I'm
a father of two and husband of one. I founded Mobile Monday London and the Mobile 2.0 conference series. I work for Vodafone where, among other things, I am
the W3C representative.
The opinions expressed here are my own, however, and neither Vodafone nor any other party necessarily agrees with them.
My books:
Mobile Internet for Dummies
XML and SQL
For more info, see my Linkedin profile.
More (probably than you ever wanted to know) about Torgo.
This work is licensed under a Creative Commons License.
I was going to ask if you had tried anything with AJAX on Opera mini - there seem to be conflicting reports about its Javascript capabilities and where it is executed.
But now you’ve moved the discussion onto Opera Mobile as well I have to ask. Specifically is there any indication on the minimum round-trip time for an AJAX request - I only ask because standard WAP page requests on most mobile phones seem to take forever.
In general Opera mini doesn’t do Ajax. There is some stuff it can handle, because it is common and treatable.
The minimum time for AJAX depends on how long it takes to send and receive the packets (which is dependent on your phone network), and how long it takes for them to be processed at the other end, as well as processing time on the phone. For small stuff, the network will be the big factor here.