Closed
Bug 632538
Opened 14 years ago
Closed 13 years ago
For the VKB, Barcode Keyboard 's next button does not move the cursor to the next field
Categories
(Firefox for Android Graveyard :: General, defect, P5)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: nhirata, Unassigned)
Details
(Whiteboard: [vkb])
1. download Barcode Keyboard Trial
2. set the system inp[ut method to Barcode Keyboard
3. close the hardware keyboard
4. go to http://people.mozilla.com/~nhirata/html_tp/formsninput.html
5. click in a field.
6. hit the next key
Expected: the next key should go to the next field
Actual: active field does not change.
![]() |
Reporter | |
Updated•14 years ago
|
Whiteboard: [vkb]
![]() |
Reporter | |
Updated•14 years ago
|
Priority: -- → P3
Updated•13 years ago
|
Priority: P3 → P5
Comment 1•13 years ago
|
||
There seems nothing wrong on our side, the Barcode Keyboard just does not provide a proper flag in the KeyDown event, which would allow us to recognize the Next action.
Taking into account that is not a very popular VKB, with medium rating on the Android Market (3.7), I'd suggest the WONTFIX resolution for this bug.
Comment 2•13 years ago
|
||
what flag is it not providing?
Comment 3•13 years ago
|
||
also, does the stock browser have the same issue with this keyboard?
Comment 4•13 years ago
|
||
(In reply to Brad Lassey [:blassey] from comment #2)
> what flag is it not providing?
http://developer.android.com/reference/android/view/inputmethod/EditorInfo.html#IME_ACTION_NEXT
=======================
public static final int FLAG_EDITOR_ACTION
Since: API Level 3
This mask is used for compatibility, to identify enter keys that are coming from an IME whose enter key has been auto-labelled "next" or "done". This allows TextView to dispatch these as normal enter keys for old applications, but still do the appropriate action when receiving them.
=======================
(In reply to Brad Lassey [:blassey] from comment #3)
> also, does the stock browser have the same issue with this keyboard?
The stock browser does not support Next action at all for any keyboard.
Comment 5•13 years ago
|
||
this is an issue with the keyboard. I don't think it is in our interest to do anything to work around their bug.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•