Closed Bug 1039985 Opened 10 years ago Closed 10 years ago

Shift state is being mistaken as caps lock state for some input sequences

Categories

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

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1031561

People

(Reporter: timdream, Unassigned)

Details

STR: 1. Go to Contact app -> New Contact 2. Focus on the "Company" field 3. Type "Hh " to move away from the beginning of the empty field. 4. Tap Shift key twice to reach caps lock state 5. Type "HHHHHHH" 6. Tap Shift key once to cancel caps lock 7. Tap Shift key once again to reach shift state 8. Try to type "Hhhhh" Expected: 1. I am able to type "Hhhhh" where the shift state is cancelled automatically when the first H is typed Actual: 1. The first H does not cancel shift state and I am typing "HHHHH". Note: Tentatively classify this as a regression -- qawanted for branch check find the regressed release.
Flags: needinfo?(rlu)
I think this is not a regression, but a feature that caused some confusion sometimes. We would not cancel the shift state if there are 2 uppercase chars before the cursor. This logic is described here, https://github.com/mozilla-b2g/gaia/blob/master/apps/keyboard/js/imes/latin/latin.js#L895
Flags: needinfo?(rlu)
Keywords: qawanted, regression
I happened to reply a similar issue, Bug 1031561, today, and I have ni'ed Omega in that bug to see if we need to refine this behavior. Thanks.
Let's dupe this to Bug 1031561, on which Omega commented that we could remove this confusing behavior.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.