User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64; Trident/4.0; GTB7.1; SLCC1; .NET CLR 2.0.50727; Media Center PC 5.0; .NET CLR 3.5.30729; .NET CLR 3.0.30618; OfficeLiveConnector.1.4; OfficeLivePatch.0.0; FDM) Steps to reproduce: tried logging into NYTimes.com, washingtonpost.com, google.com using Swype KB (but manually typing each individual letter) in Aurrora 9.0a2 on a GalTab 10.1 / Android 3.1 Actual results: in addition to the already filed bug on spaces being added (that happened) it completely mangled what I was typing and would not allow me to correct it using backspace and re-type of input. what showed up in the emaill / userID box resembled nothing simillar to anything I typed. Expected results: it should have taked my userID / email and let me move on to password field (which seems to have worked fine) -- so bad email / userID, good password entry

This appears to be a general bug with respect to any text input field in Firefox on Android using Swype. As you select characters, Swype guesses the word and presents options. If the word choice Swype favors is wrong, you have the opportunity to select the correct one or to use the backspace/delete "key" to remove characters that were mistyped. In Firefox, the entire word gets selected, then pressing the backspace key will cause the word to be partially removed and then repeated within the remaining characters. No amount of using the delete/backspace key will allow the user to delete the word and the resulting copies of it. I end up having to change input type and going to the stock keyboard. This makes Firefox unusable for me. According to the Swype beta on-forum experts, "Unfortunately that looks like an application bug in the text field to me- it's supposed to delete the original word and replace it with the underlined version, it appears to not have done the deletion. That's likely a result of the application not supporting the InputConnection call we use, but still claiming it does by returning true."

Thanks for the bug report. Another user reported the same problem (bug 691163). Can you please comment in that bug to let us know what device and what version of Swype you are using?

Not really a duplicate. Different bug, but will respond in 691163 anyway.

Oops, you are right. This is a separate issue. Let's keep the discussion here. Sorry!

Too late! :-) Delete the comment I just left on 691163 (or ignore it) Device: Droid X OS: Android 2.3.3, Apps: Swype 3.25.91.31127 Firefox 7.0.1

gekko, your problem (comment 1) sounds like bug 672661 which is fixed in Firefox 9, currently on the Aurora channel. You can download an Aurora build from http://www.mozilla.org/firefox/channel/ to see if it is fixed. Stefan, can you give more details of what happens when you type in one of these username fields in Swype on Aurora? (For example, "I pressed the keys A, B, C, but then BCA appeared in the text box instead.") Does this also happen in other form fields, like the search box at http://www.google.com/ ?

Samsung GalTab 10.1 3G (unlocked) / Android 3.1 (kernel 2.6.36.3) / Swype 3.9.86.2784 Something in last night's build (in some other area) seems to have fixed this bug -- cannot reproduce today.

Thanks to the pointer to Aurora. Loaded 9.0a2. I now see spaces being added following each character entry, increases lag in the interaction with Swype dictionary, and a continuation of the issue with the backspace key. You are correct, though, that bug 672661 appears to be the bug I am witnessing in FF 7. I'll monitor that thread, thanks.

(In reply to gekko from comment #8) > You are correct, though, that bug 672661 appears to be the bug I am > witnessing in FF 7. I'll monitor that thread, thanks. Backspace bug was fixed - you can try the Nightly build, which has all the latest fixes. It is available here: http://nightly.mozilla.org/ But input with Swype in general is still an issue. I guess this "mangling" text problem is similar to bug 691163, they are of the same nature. It seems like Swype detects the end of the word too early, sometimes after each character, so it adds a space and/or tries to fix an incomplete word. For example, it's fixing "incorrectly" entered one-letter "words", replacing them with "correct" ones "a" or "I". The keys surrounding "a" and "i" on the keyboard are mostly affected by this.

Doesn't happen with native UI.

I get this same behavior with other keyboards as well, have currently tried SwiftKey and Thumb Keyboard on the latest nightly build. Arrow keys don't work, cursor moves randomly and adds random characters, can't correct words, etc.

(In reply to Matt Cosentino from comment #11) > I get this same behavior with other keyboards as well, have currently tried > SwiftKey and Thumb Keyboard on the latest nightly build. Arrow keys don't > work, cursor moves randomly and adds random characters, can't correct words, > etc. Matt, does all this happen with the latest native UI nightly? Those builds are available here: http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/latest-birch-android/

Closing all opened bug in a graveyard component