S60 Opera Mobile 10 Text Entry Bug and Workarounds

Opera Mobile S60 10 Beta 2 Update Edit Bug

Ah, the joys of beta software.  It turns out that the  Beta 2 "Update"  release of Opera Mobile 10 that I raved about last week has a bug that inserts random text in mult-line edit fields. It's bad enough to make using Web-mail and most online Twitter clients almost impossible.

The problem occurs as soon as you type text that extends beyond the width of the screen. When Opera wraps the text to the next line it also copies part of what was typed into the new line. With every new line Opera copies more and more text, quickly makeing unreadable gobbledygook of what you are typing.  The screen shot shows the results of typing "The quick brown fox jumps over the lazy dog"  three times.

To make matters worse, the ability to disable in-line editing and use the phone's native editor in a separate  window, which would be a usable workaround, was removed from the Update release.

Opera has acknowledged the issue and I'm sure it will be fixed in the next release.  I'm not expecting that the fix will available until after the holidays. I certainly don't want to see the Opera Mobile development and QA staff slaving away while the rest of us are celebrating with our families.

In the meantime there are a few rather ugly workarounds.

  • Manually enter a return at the end of each line before the text wraps.  This works but is tricky. If you don't enter the return in time the bug fires and cleaning up the resulting mess is almost impossible.
  • For Twitter,  if you use Dabr switch to Tweete which uses a single line field for entering Tweets and therefore is bug-free.
  • Compose text in the Nokia Notes app and paste it into Opera Mobile.  Pasted text is not effected by the  bug as long as you don't try to edit it.
  • Revert back to the pre-Update version of Opera Mobile 10 which is available from Opera's FTP site.

I plan to continue use the Update release because I want to contribute to its development by bug reporting any other issues that I find. Plus I don't do a lot of posting to forums, web-mail or commenting on blogs using my N95, preferring to use the virtual QWERTY of my Android phone.  However, if you do a lot of long form data entry on your S60 phone I recommend that you stay with or roll back to the pre-Update version of Beta 2. Incidentally, the Windows Mobile Opera 10 Beta 2 Update does not suffer from this bug so WinMo users should not hesitate to update.

6 thoughts on “S60 Opera Mobile 10 Text Entry Bug and Workarounds

  1. I'm using the latest beta right now to write this reply. I own a Nokia E63 which is no different to E71 and I've found an easy fix for OperaMobile10 issues. In previous beta you had to press #8 and enable/disable inline editing but this version allows you to do that by pressing and holding the center key on a textbox. easy.
  2. I did a lot of effort to work with opera mobile beta. It looks more like an Alpha 1. It is full of bugs. Some websites will not be shown at all. Some look great. I found it impossible to add my websites to the quick start list with my own key board. It only works with the f.... Opera key board. I do not understand the policy not to enable video support in anyway. Opera mobile is web browsing of the 90s. I hope skyfire and the soon to come firefox browser will proove a lot better.
    Nokia 5800 xpress music.
  3. i agree with you, beta 2 has to be better, but it's snappier on my e71. I can't really figure out why, but the interface/buttons get stuck for a second or two (always!). Thanks a lot for finding the link to beta 1. (Now, I've completely switched to opera mobile and skyfire now.)
  4. There are no Opera Mini files on the FTP site.

    Why would you want to revert to Beta 1? Opera Mini Beta 2 doesn't suffer from text editing bug, only Opera Mobile. Mini's Beta 2 is huge improvement over Beta 1 (Opera Link, Download Manager, easy toggle between inline and fullscreen edit, reduced memory requirements and a lot more).

    If you really want Beta 1 the files are here:
    Those are for the unsigned version, I couldn't find the signed ones anywhere unfortunately.

Leave a Reply

Your email address will not be published. Required fields are marked *