Closed
Bug 805735
Opened 13 years ago
Closed 13 years ago
[Keyboard] Cannot input SIM PIN or number with input[type=number]
Categories
(Firefox OS Graveyard :: Gaia, defect, P1)
Tracking
(blocking-basecamp:+)
VERIFIED
FIXED
| blocking-basecamp | + |
People
(Reporter: rudyl, Assigned: rudyl)
References
Details
Attachments
(1 file)
|
203 bytes,
text/html
|
timdream
:
review+
vingtetun
:
approval-gaia-v1+
|
Details |
STR
===
1. Reboot the phone.
2. Go UI test > keyboard.
3. pick a input of type number, then focus to get the keyboard shown.
4. type some numbers.
Expected:
The numbers would be shown on the input field.
Actual:
nothing shown.
--
This issue also applies to SIM PIN input.
| Assignee | ||
Comment 1•13 years ago
|
||
[Approval Request Comment]
User impact if declined: Cannot input numbers.
Testing completed: yes
Root cause:
the CapsLock key element may not exist when the keyboard is shown as number for the first time.
In showKeyboard(), resetKeyboard() failed due to the above case, and then we failed to invoke inputMethod.activate().
Attachment #675478 -
Flags: review?(timdream+bugs)
Attachment #675478 -
Flags: approval-gaia-master?(21)
Comment 2•13 years ago
|
||
Comment on attachment 675478 [details]
pullRequest 6013
r=me.
Attachment #675478 -
Flags: review?(timdream+bugs) → review+
Comment 4•13 years ago
|
||
Looks like I didn't test my keyboard patch thoroughly enough. I'm happy that I've got great colleagues to clean up after me!
I agree with Chris that the patch would be better without the console.warn call.
| Assignee | ||
Comment 5•13 years ago
|
||
Hi David,
The cosole.warn() has been removed as Chris and you suggested.
Thank you.
Comment 7•13 years ago
|
||
Comment on attachment 675478 [details]
pullRequest 6013
Can not type number? Solved with a one liner js. a=me.
Attachment #675478 -
Flags: approval-gaia-master?(21) → approval-gaia-master+
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
blocking-basecamp: ? → +
Priority: -- → P1
Comment 8•12 years ago
|
||
This issue fixed for device Ungia; build #20130102070202 v.1
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•