STR: 1. Using Galaxy SII, load a website with text input form 2. Rotate device to landscape orientation 3. Select text input form and start typing AR: The cursor jumps from the end of the text back to position 0 after every character entered, but the entered text is correct.
tracking-fennec: --- → ?
status-firefox15: --- → affected
Not just Galaxy SII. Any device that has a small enough screen to use the extracted text IME for landscape VKB (such as Galaxy SII and Droid Pro) is affected. I suspect the problem is that Gecko and the extracted text IME have different understandings of the current selection because we might not be tracking the text updates in the extracted text IME.
Summary: Galaxy SII's extracted UI IME (landscape VKB) displays cursor at incorrect position (but entered text is correct) → Landscape VKB using "extracted text" IME displays cursor at incorrect position (but entered text is correct)
In my case, the entered text is not correct due to the jumping cursor.
tracking-fennec: ? → ---
status-firefox15: affected → ---
By the above comment I meant I can reproduce the bug in my Galaxy S2 with Android 2.3.4 and Nightly 15 0a1 (05-31-2012), and also that I think the jumping cursor is the problem because in my case it changes the password's characters order making it impossible to sign in correctly in any site because of the wrong password.
I see this on a samsung galaxy ace 2. Another consequence of the bug is that if I write a comment longer than the text input box, the view stays with the cursor at the beginning of the entry - instead of scrolling so that the last line is in view - so that I'm writing blind.
I'm seeing this again using today's Nightly in a web text field. Seems to happen only in the following site though (I've tried several other sites) https://m.ups.com/mobile/ratetnthome?loc=en_US The cursor always goes back to the left of the last typed letter, so the words get written backwards: "anitnegrA" instead of "Argentina".
Gabriela, thanks for catching this problem! I made a change to this code last night. I can repro the "anitnegrA" bug with Nightly 18.0a1 2012-09-06 on my Galaxy S II using the default Samsung Keyboard. I can't repro the problem using Swype or MultiLing Keyboard on my Galaxy S II. I can't repro on my Droid Pro. So the problem seems to be something the Samsung Keyboard is doing in Extracted Text landscape mode that is confusing us.
hmm, I am no longer able to repro this bug. There must be a timing issue that makes this bug intermittent. :(
I can repro this bug again if I enable the Samsung Keyboard's "XT9 Predictive Text" setting.
status-firefox15: --- → affected
status-firefox16: --- → affected
status-firefox17: --- → affected
status-firefox18: --- → affected
Version: unspecified → Firefox 15
Assignee: nobody → cpeterson
Status: NEW → ASSIGNED
I checked with today's Nightly and Samsung's default keyboard. In portrait mode, I cannot reproduce the bug: the cursor doesn't jump from the end of the text back to position 0 after every character entered at all and every thing works fine so I can log in to Hotmail for example. In landscape mode however, I can still reproduce it: the cursor jumps from the end of the text back to position 0 after every character entered, but the entered text is correct (unlike before when the letters ended written backwards) so I can login correctly despite the jumping cursor.
I can still reproduce the bug in the latest Nightly (Firefox 19), only in ladnscape mode though, but it has gone back to the stage the cursor is always going back to the left of the last typed letter, so the words get written backwards: "anitnegrA" instead of "Argentina".
Assignee: cpeterson → nobody
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.