489853 - missing characters while typing in URL via softkeyboard

Status: VERIFIED FIXED

(Firefox for Android Graveyard :: General, defect)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

If I click in the URL bar the soft keyboard is displayed and I can type in a new url.  I click with the stylus kayak.com, but sometimes characters are missed. 

I have noticed this many times and it appears to be related to the awesome bar loading up.  For some reason typing the characters on the hard keyboard works just fine.

Comment 1

[Doug Turner (:dougt)]

what are the steps to reproduce?

Comment 2

[Joel Maher ( :jmaher ) (UTC -8)]

1) click in the URL bar
2) using the soft keyboard, type kayak.com
3) observe missing characters

If you wait 20 seconds between steps 1 and 2, this problem goes away (at least for the speed that I can type characters).

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

I am still seeing this on winmo alpha2 candidate build on 6/25

Comment 4

[Joel Maher ( :jmaher ) (UTC -8)]

I keep running into this with the latest a3 builds

Comment 5

[Joel Maher ( :jmaher ) (UTC -8)]

I have an unlocked HTC Touch Pro (not Fuze or carrier specific).

ROM Version: 5.05.405.1 WWR
ROM Date:  03/04/09
Radio version: 1.11.25.1
Protocol version: 52.58.25.30U
Model NO:  HTC Touch Pro T7272

Comment 6

[Doug Turner (:dougt)]

Hey Joel -- which Software Keyboard are you using?  Have you tried different ones?  Do they all behave the same?

Comment 7

[Joel Maher ( :jmaher ) (UTC -8)]

I tried with 3 different keyboards and no luck :(  As I stated before, this is related to the awesomebar doing the searching, so when I type it is working on filtering the results.

also this bug is blocking 1.0a2-wm+, what does that mean?  That doesn't sound like it is really blocking if we shipped 1.0a2 without it...can we get it to really block beta1?

Comment 8

[Mark Finkle (:mfinkle) (use needinfo?)]

from IRC:

jmhaer: As soon as the awesomebar doesn't match, every character is recognized in real time

Comment 9

[Joel Maher ( :jmaher ) (UTC -8)]

and doing this with a "full qwerty" keyboard in portrait mode.

Comment 10

[Aakash Desai [:aakashd]]

Yep, I see this issue on the Omnia 1 and 2. This is a performance bug on WinMo devices.

Comment 11

[Doug Turner (:dougt)]

joel, blassey tells me that this may have been fixed by the async awesome bar stuff.

Comment 12

[Joel Maher ( :jmaher ) (UTC -8)]

doug, yeah I verified a private build blassey gave me and it worked very well.

Comment 13

[Doug Turner (:dougt)]

has the async stuff landed on 192?  can we verify the fix.

Comment 14

[Brad Lassey [:blassey] (use needinfo?)]

It appears that bug 514968 resolved this issue.

Comment 15

[Joel Maher ( :jmaher ) (UTC -8)]

verified with 20090911 1.9.2 nightly build on my htc touch pro.

Comment 16

[Shawn Wilsher :sdwilsh]

(In reply to comment #14)
> It appears that bug 514968 resolved this issue.
How?

Comment 17

[Shawn Wilsher :sdwilsh]

(In reply to comment #13)
> has the async stuff landed on 192?  can we verify the fix.
Yes - it landed in bug 455555