1034942 - [OPEN_C][v1.4] Keyboard autocomplete makes the caps lock turn on permanently

Status: RESOLVED DUPLICATE of bug 1036075

(Firefox OS Graveyard :: Gaia::Keyboard, defect)

Description

[Anton Borodyuk]

Attachment: Bug in action, I didn't touch the shift button

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Firefox/31.0 (Beta/Release)
Build ID: 20140703154127

Steps to reproduce:

* Open browser.
* Get a web page with a text field (I was able to reproduce it in google groups and on https://support.mozilla.org).
* Type some stuff.
* Use autocomplete a few times until the keyboard go nuts.


Actual results:

This bug happens mostly in a browser when typing in a text field like this I'm currently typing into.
When typing words there's a chance that autocomplete will go nuts and after you autocomplete the word the caps lock will turn on indefinitely. It does not look like caps lock is turned on (the shift key does not have the line indicating it's caps locked), rather it just makes every letter uppercase instead. So after I type a letter, the next one becomes upper case if I don't click shift again.


Expected results:

Letters should become upper case automatically only after a dot.

Comment 1

[Anton Borodyuk]

I forgot to add. Running latest Firefox OS from 1.4 branch on ZTE Open C.

Comment 2

[nick]

Caps lock sometimes turns on for the duration of the session in the window using keyboard, i.e., if I save a message as draft or flip to another window and flip back, caps lock is disabled. When this bug occurs, single-tapping SHIFT allows for creating one lowercase character but immediately returns to caps lock.

I can't deliberately replicate this bug. It must have something to do with autocomplete and appears to me to present when a period appears with a space between it and the last character in a sentence, like this . That's when the problems start.

Running B2G 2.1.0.0-prerelease WITHOUT locale support.

Comment 3

[nick]

This is on a Nexus 4 (Mako).

Comment 4

[Johan Lorenzo [:jlorenzo]]

Thank you for reporting this bug. I have reported the same 3 days after you so mine should have been marked as a duplicate of yours. A fix is already proposed in bug 1036075 though. We'll track the fix with that bug then.