Closed
Bug 879076
Opened 11 years ago
Closed 11 years ago
[keyboard] nearby key data is sometimes in uppercase instead of lowercase
Categories
(Firefox OS Graveyard :: Gaia::Keyboard, defect)
Tracking
(b2g18 fixed)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
b2g18 | --- | fixed |
People
(Reporter: djf, Assigned: djf)
References
Details
(Keywords: regression)
Attachments
(1 file)
For auto correction the keyboard sends a map of what keys are near what other keys to the prediction engine. This map is supposed to be based on lowercase keycodes. But sometime recently (presumably as a result of the recent keyboard all-uppercase change) it has changed and now sometimes it sends an uppercase-based map.
When we have a bad nearby key map we get corrections that do not take nearby keys into account. When we have a valid key map, we get better suggestions.
To reproduce this bug open the UI tests app, click on keyboard tests and type 'ch' into a field. It should suggest 'cha'. Now tap on another field (or lock the phone and then return to the app) and type 'ch' again. This time you get VH. (I don't know what that is an abbreviation for, but it is the correct suggestion.
Other examples include s->a when the keyboard map is correct and s->s when it is not.
Assignee | ||
Updated•11 years ago
|
Assignee | ||
Comment 1•11 years ago
|
||
Actually, this has to do with auto-capitalization. In text areas, we autocapitalize and are getting uppercase letters in the nearby keys. In textfields by default we do not auto capitalized and don't have this bug. In a text area after if you're in lowercase and sleep the screen and wake it back up you'll get a new nearby keys data, and it will work.
Assignee | ||
Comment 2•11 years ago
|
||
Attachment #757732 -
Flags: review?(eshapiro)
Attachment #757732 -
Flags: review?(eshapiro) → review+
Assignee | ||
Comment 3•11 years ago
|
||
Landed on master: https://github.com/mozilla-b2g/gaia/commit/60d03c4ff2570844f868a7bedcd8b5249e3b27ea
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Comment 4•11 years ago
|
||
On the latest master build I am still getting different nearby key data after causing the device to sleep and then returning. Just as in the decription, I entered "Ch" and received "Cha" as a suggestion but after causing the device to sleep I received "VH" as a suggestion forthe same characters.
Tested on b2g/nightly/mozilla-central-unagi/latest.
Kernel Date: Dec 5
Gecko: http://hg.mozilla.org/mozilla-central/rev/3c6f2394995d
Gaia: d2ad0f1a5a6be8a2d6df721ba3c2b33e037c423b
Assignee | ||
Comment 5•11 years ago
|
||
(In reply to Chris Schmoeckel from comment #4)
> Tested on b2g/nightly/mozilla-central-unagi/latest.
>
> Kernel Date: Dec 5
> Gecko: http://hg.mozilla.org/mozilla-central/rev/3c6f2394995d
> Gaia: d2ad0f1a5a6be8a2d6df721ba3c2b33e037c423b
I flashed my unagi with the nightly build too, but have a different gaia commit. This one is from Friday 5/31!
Updated•11 years ago
|
Flags: in-moztrap?(cschmoeckel)
Comment 7•11 years ago
|
||
Added Keyboard Suite Test Case #8482 - [Keyboard] Navigating away and back to the text field does not reset capitalization
Flags: in-moztrap?(cschmoeckel) → in-moztrap+
You need to log in
before you can comment on or make changes to this bug.
Description
•