Closed
Bug 489853
Opened 15 years ago
Closed 15 years ago
missing characters while typing in URL via softkeyboard
Categories
(Firefox for Android Graveyard :: General, defect)
Firefox for Android Graveyard
General
ARM
Windows Mobile 6 Professional
Tracking
(fennec1.0b1-wm+)
VERIFIED
FIXED
Tracking | Status | |
---|---|---|
fennec | 1.0b1-wm+ | --- |
People
(Reporter: jmaher, Assigned: dougt)
Details
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.
Reporter | ||
Updated•15 years ago
|
tracking-fennec: --- → ?
Updated•15 years ago
|
tracking-fennec: ? → 1.0a2-wm+
Assignee | ||
Comment 1•15 years ago
|
||
what are the steps to reproduce?
Reporter | ||
Comment 2•15 years ago
|
||
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).
Reporter | ||
Comment 3•15 years ago
|
||
I am still seeing this on winmo alpha2 candidate build on 6/25
Reporter | ||
Comment 4•15 years ago
|
||
I keep running into this with the latest a3 builds
Reporter | ||
Comment 5•15 years ago
|
||
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
Assignee | ||
Comment 6•15 years ago
|
||
Hey Joel -- which Software Keyboard are you using? Have you tried different ones? Do they all behave the same?
Reporter | ||
Comment 7•15 years ago
|
||
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?
Updated•15 years ago
|
tracking-fennec: 1.0a2-wm+ → 1.0b1-wm+
Updated•15 years ago
|
Assignee: nobody → doug.turner
Comment 8•15 years ago
|
||
from IRC: jmhaer: As soon as the awesomebar doesn't match, every character is recognized in real time
Reporter | ||
Comment 9•15 years ago
|
||
and doing this with a "full qwerty" keyboard in portrait mode.
Comment 10•15 years ago
|
||
Yep, I see this issue on the Omnia 1 and 2. This is a performance bug on WinMo devices.
Assignee | ||
Comment 11•15 years ago
|
||
joel, blassey tells me that this may have been fixed by the async awesome bar stuff.
Reporter | ||
Comment 12•15 years ago
|
||
doug, yeah I verified a private build blassey gave me and it worked very well.
Assignee | ||
Comment 13•15 years ago
|
||
has the async stuff landed on 192? can we verify the fix.
Comment 14•15 years ago
|
||
It appears that bug 514968 resolved this issue.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 15•15 years ago
|
||
verified with 20090911 1.9.2 nightly build on my htc touch pro.
Status: RESOLVED → VERIFIED
Comment 16•15 years ago
|
||
(In reply to comment #14) > It appears that bug 514968 resolved this issue. How?
Comment 17•15 years ago
|
||
(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.
Description
•