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.
what are the steps to reproduce?
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).
I am still seeing this on winmo alpha2 candidate build on 6/25
I keep running into this with the latest a3 builds
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: 126.96.36.199 Protocol version: 188.8.131.52U Model NO: HTC Touch Pro T7272
Hey Joel -- which Software Keyboard are you using? Have you tried different ones? Do they all behave the same?
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?
from IRC: jmhaer: As soon as the awesomebar doesn't match, every character is recognized in real time
and doing this with a "full qwerty" keyboard in portrait mode.
Yep, I see this issue on the Omnia 1 and 2. This is a performance bug on WinMo devices.
joel, blassey tells me that this may have been fixed by the async awesome bar stuff.
doug, yeah I verified a private build blassey gave me and it worked very well.
has the async stuff landed on 192? can we verify the fix.
It appears that bug 514968 resolved this issue.
Status: NEW → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → FIXED
verified with 20090911 1.9.2 nightly build on my htc touch pro.
Status: RESOLVED → VERIFIED
(In reply to comment #13) > has the async stuff landed on 192? can we verify the fix. Yes - it landed in bug 455555
You need to log in before you can comment on or make changes to this bug.