Closed Bug 709073 Opened 13 years ago Closed 13 years ago

Text input very slow, janky

Categories

(Firefox for Android Graveyard :: General, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 595008

People

(Reporter: johnath, Unassigned)

Details

(Keywords: inputmethod, Whiteboard: [VKB])

STR: 1) Open zimbra mobile because you hate yourself a little 2) Compose new message 3) Type in content field On my galaxy s2, text input is very slow, and also features lots of jumpiness apparently associated with the keyboard's word prediction - in-text selections appearing and disappearing frequently. The keyboard itself is unresponsive during this, too: haptic and visual feedback on keypresses lag. It's pretty unpleasant to use. Hard to tell definitively, but this might be worse still in reply emails, where the textarea has lots of content, but that could be illusory. On DolphinHD (sigh) input is responsive and jank-free.
(In reply to Johnathan Nightingale [:johnath] from comment #0) > On my galaxy s2, text input is very slow, and also features lots of > jumpiness apparently associated with the keyboard's word prediction - > in-text selections appearing and disappearing frequently. The keyboard > itself is unresponsive during this, too: haptic and visual feedback on > keypresses lag. It's pretty unpleasant to use. I tried on Nexus One and Droid 3 - it doesn't seem too bad. Maybe just a bit slow, but still very usable. Johnathan, what kind of VKB are you using, and what version? I'd guess it's Swype - this IME is usually slower than the others.
Keywords: inputmethod
Whiteboard: [VKB]
This was with swiftkey, lemme throw a new nightly on and see how it varies between keyboards.
Yeah - I confirm that the system keyboard is not-perfect-but-much-better. Having said that, swiftkey doesn't slow down the system browser at all.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.