Closed Bug 683767 Opened 13 years ago Closed 13 years ago

Text input incompatibility with flext9

Categories

(Firefox for Android Graveyard :: General, defect)

Firefox 6
ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: satkins01, Assigned: alexp)

Details

(Keywords: inputmethod)

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0) Gecko/20100101 Firefox/6.0
Build ID: 20110811165603

Steps to reproduce:

Using the FlexT9 keyboard application (https://market.android.com/details?id=com.nuance.flext9.input), editing text in html <input type="text" /> fields is problematic.

Example:
(Install and activate flext9)
Go to google.com, enter a word into the search field and press space.
Attempt to backspace into the word.


Actual results:

Backspacing removes the entire word, the keyboard then presents word suggestions as if the user had entered the word which was removed, then immediately after the word is replaced in the text field.

With FlexT9's autocorrect disabled, the above happens twice and THEN allows editing of the word.

(It should be noted that I have never experienced issues with this keyboard in any other application besides Fennec, implying that this is an issue with how Fennec handles keyboard input, not in the keyboard itself.)


Expected results:

Backspacing into a word should either remove the entire word (without replacing it) or erase the last character of the word. (Obviously)
Please check against the Firefox beta from the market that has the fix for bug 667927.
OS: Windows 7 → Android
Hardware: x86_64 → ARM
Using beta from market does not resolve issue.
I should note:
Observed on HTC Desire HD, Android 2.3
Keywords: inputmethod
I believe this issue is similar to the problems we are facing with SwiftKey (bug 672661). Needs to be investigated though to confirm what exactly is happening there.
Assignee: nobody → alexp
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
It should be fixed in native UI now.
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.