Closed Bug 801645 Opened 13 years ago Closed 13 years ago

backspace deletes wrong text exactly after selecting a suggested word

Categories

(Firefox for Android Graveyard :: Keyboards and IME, defect)

Product:
Firefox for Android Graveyard
Component:
Keyboards and IME
Version:
16 Branch
Platform:
ARM
Android
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(firefox16 affected, firefox17 affected, firefox18 affected, firefox19 affected)

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox16 --- affected
firefox17 --- affected
firefox18 --- affected
firefox19 --- affected

People

(Reporter: tspiteri, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20100101 Firefox/16.0 Build ID: 20121011153927 Steps to reproduce: This is on Android Jelly Bean (on a Nexus 7). In a text area, I start to type text. If by mistake I choose the wrong word from the suggestions right above the keyboard, and then touch backspace, the wrong text is deleted. Sometimes the whole contents of the text area is deleted.
OS: Linux → Android
Hardware: x86_64 → ARM
Which build was tested? Have you tried Nightly? (http://nightly.mozilla.org)
Component: General → Keyboards and IME
I have tested on 16.0.1 and now I've also tested on the nightly 19.0a1 (2012-10-15). The bug is on both. For example, I go to google.com, then tap on the field and start typing: t h <tap on "this"> i s <tap on "is">. Now, "this is" is displayed in the text area. If I tap on backspace, only "this " is deleted. This is not the only one example, backspace behaves strangely in other cases as well, even without using the suggested words. For example, if I type "a b c d" followed by three backspaces, the first two backspaces correctly delete " d", but the third backspace deletes "a b " and leaves "c".
Version: Firefox 15 → Firefox 16
Status: UNCONFIRMED → NEW
Ever confirmed: true
After a bit of searching, I think it's more related to bug 790631.
I have a stock Galaxy Nexus (the Play Store version), on the stock keyboard set to aggressive auto-correct, and have experienced this same bug the entire time I've been using the official FF releases on it (August '12). It is highly infuriating. What logs can I provide to assist debugging this?
tracking-fennec: --- → ?
status-firefox16: --- → affected
status-firefox17: --- → affected
status-firefox18: --- → affected
status-firefox19: --- → affected
qawanted to retest after jchen's thread safe IME has landed. renom if it still exists
Keywords: qawanted
I cannot reproduce the bug on the nightly build 19.0a1 (2012-11-03).
Status: NEW → RESOLVED
Closed: 13 years ago
Keywords: qawanted
Resolution: --- → WORKSFORME
tracking-fennec: ? → ---
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.