Closed Bug 947558 Opened 12 years ago Closed 11 years ago

[keyboard] Short tap on the keyboard does not show lower case; inconsistent with long tapping on the key and showing the lower case accented characters

Categories

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

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog, b2g18 unaffected, b2g-v1.3 affected)

RESOLVED DUPLICATE of bug 985333
tracking-b2g backlog
Tracking Status
b2g18 --- unaffected
b2g-v1.3 --- affected

People

(Reporter: nhirata, Unassigned)

References

Details

(Keywords: uiwanted, Whiteboard: [ft:system-platform])

Gaia: 8fca2ca67e8a6022fe6ed8cb576e5d59dfb5237f Gecko: http://hg.mozilla.org/mozilla-central/rev/1401e4b394ad BuildID 20131206040203 Version 28.0a1 ro.build.version.incremental=eng.archermind.20131114.105818 Buri 1. launch browser 2. tap in url bar 3. long tap on the k key (it shows a capital K instead of a small k even though the shift key hasn't been toggled) 4. release the k key ( you will see a small k) 5. long tap on e key. Expected: there's consistency with the accented letters and the non accented letters to be all lower case for the highlight Actual: the accented letters are lower case, the initial nonaccented keys are upper case.
Summary: [keyboard] Short tap on the keyboard does not show lower case; inconsistent with long tapping on the key. → [keyboard] Short tap on the keyboard does not show lower case; inconsistent with long tapping on the key and showing the lower case accented characters
blocking-b2g: --- → 1.4?
Keywords: uiwanted
Is this present on 1.3?
Keywords: qawanted
This issue reproduces on v1.3 v1.3 Environmental Variables: Device: Buri v1.3 MOZ BuildID: 20140305004003 Gaia: 9b29f80309212bd80fbdcf2882458b1ae8b30093 Gecko: b3478af0151e Version: 28.0 Firmware Version: v1.2-device.cfg
Keywords: qawanted
QA Contact: pbylenga
What about 1.1?
Keywords: qawanted
This issue does not reproduce in 1.1. Note there was a style change from lower case on the keys to upper case which affects the reproduction of the issue. 1.1 Environmental Variables: Device: Buri 1.1 MOZ BuildID: 20140218041202 Gaia: c5cb252e5d1aa45d14f3a2ea182e73e2271e4496 Gecko: d7f2811943d1 Version: 18.0 Firmware Version: v1.2-device.cfg
Ivan Please help with reassigning for keyboard issues.
blocking-b2g: 1.4? → 1.3+
Flags: needinfo?(itsay)
Why is this a blocker? It's backlog at best, but I'm not even sure it's a bug.
blocking-b2g: 1.3+ → 1.3?
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
blocking-b2g: 1.3? → ---
This isn't a dupe of bug 883340. This was filed for an inconsistency of behavior from switching to a pure uppercase keyboard.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
It is the current keyboard design since we changed the keyboard to upper case in v1.2. UX team is proposing an improvement on this inconsistency of the highlight effect when short or long tap the key. Also ni? Mike for the comments from UX team. For now, put this in backlog of system platform keyboard work.
Blocks: 908549
blocking-b2g: --- → backlog
Flags: needinfo?(itsay) → needinfo?(mtsai)
Whiteboard: [ft:system-platform]
Please see the latest spec as an attachment (p.7) in https://bugzilla.mozilla.org/show_bug.cgi?id=983043
Flags: needinfo?(mtsai)
It's a blocker due to end user demand on sumo as well as in bugzilla that they want some sort of lower case feedback. It is now a feature for 1.5 : bug 985333
Status: REOPENED → RESOLVED
Closed: 11 years ago11 years ago
Resolution: --- → DUPLICATE
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.