Closed
Bug 1021500
Opened 11 years ago
Closed 11 years ago
[Keyboard] Keyboard for Email shouldn't have '_' in the second row
Categories
(Firefox OS Graveyard :: Gaia::Keyboard, defect, P1)
Tracking
(b2g-v2.1 verified)
VERIFIED
FIXED
| Tracking | Status | |
|---|---|---|
| b2g-v2.1 | --- | verified |
People
(Reporter: Omega, Assigned: raniere)
References
Details
(Whiteboard: [2.0-FL-bug-bash])
Attachments
(2 files)
|
46 bytes,
text/x-github-pull-request
|
janjongboom
:
review+
Omega
:
ui-review+
|
Details | Review |
|
1.56 MB,
video/mp4
|
Details |
Device: Flame
Gaia: 2014-06-05 23:34:17
BuildID: 20140602160205
Version: 2.0.0.0-prerelease
STR:
1) Tap any "email" input to show keyboard
Actual:
There is '_' key in the second row
Expected:
There shouldn't be '_' key in the second row
| Reporter | ||
Updated•11 years ago
|
Whiteboard: [2.0-FL-bug-bash]
Comment 1•11 years ago
|
||
Based on? Is there a UI document that says this should be removed?
Flags: needinfo?(ofeng)
| Reporter | ||
Comment 2•11 years ago
|
||
(In reply to Jan Jongboom [:janjongboom] (Telenor) from comment #1)
> Based on? Is there a UI document that says this should be removed?
Hi Jan,
There is no UI spec that says '_' should be there, so we should remove it to keep the layouts (normal text and email) consistent.
Flags: needinfo?(ofeng)
| Reporter | ||
Updated•11 years ago
|
Blocks: keyboard-ux-update
| Assignee | ||
Comment 3•11 years ago
|
||
Attachment #8435773 -
Flags: ui-review?(ofeng)
Attachment #8435773 -
Flags: review?(janjongboom)
| Reporter | ||
Comment 4•11 years ago
|
||
Comment on attachment 8435773 [details] [review]
patch-remove-extra-keys-from-second-row
Good job! Thanks!
Attachment #8435773 -
Flags: ui-review?(ofeng) → ui-review+
Comment 5•11 years ago
|
||
Comment on attachment 8435773 [details] [review]
patch-remove-extra-keys-from-second-row
Clearing review for now. This only solves it for English but all other layouts have the same configuration. We should fix it for all layouts.
Attachment #8435773 -
Flags: review?(janjongboom)
| Assignee | ||
Comment 6•11 years ago
|
||
Some questions, although they are very similar.
1. For Spanish, the second row for email and url should have "ñ"?
2. For Catalan, Croatian, Hungarian and Serbian, the second row for email and url should have "'"?
3. For Portuguese, the second row for email and url should have "ç"?
Note: The patch was update by preserving this keys at email and url input type.
Flags: needinfo?(ofeng)
| Reporter | ||
Comment 7•11 years ago
|
||
(In reply to Raniere Silva from comment #6)
> Some questions, although they are very similar.
> 1. For Spanish, the second row for email and url should have "ñ"?
> 2. For Catalan, Croatian, Hungarian and Serbian, the second row for email
> and url should have "'"?
> 3. For Portuguese, the second row for email and url should have "ç"?
Yes to all three questions. "ñ", "'" and "ç" are valid (or limited supported) in URL and email address, so we should keep them.
Flags: needinfo?(ofeng)
| Assignee | ||
Comment 8•11 years ago
|
||
Hi Jan, could you review the patch again? It should fix this issue for all layouts now.
Flags: needinfo?(janjongboom)
Updated•11 years ago
|
Attachment #8435773 -
Flags: review?(janjongboom)
Flags: needinfo?(janjongboom)
Comment 9•11 years ago
|
||
Comment on attachment 8435773 [details] [review]
patch-remove-extra-keys-from-second-row
r=me. Looks good. Thanks!
Attachment #8435773 -
Flags: review?(janjongboom) → review+
Comment 12•11 years ago
|
||
Flags: needinfo?(janjongboom)
| Reporter | ||
Comment 13•11 years ago
|
||
It's a major issue in new feature. Nominating as 2.0 blocking.
A consistent layout is really important for a large number of users.
blocking-b2g: --- → 2.0?
Comment 14•11 years ago
|
||
I discussed this bug (and others like it) with Jason in IRC today. This looks like a 2.0 feature that was not correctly or fully implemented to spec, and should not ship as-is as a result (per Omega's comment #13). To that end, I am removing the blocking flag but adding the feature-b2g flag for 2.0, which it looks like this bug should have had as it was on the work list for 2.0. If this is not correct, let me know and we can discuss making it a blocking bug if it was not indeed a feature.
I am not sure why the attachment has ui-review+ if the UI is not correct. When there is a major issue like this with a patch, the patch should get ui-review- and only get a ui-review+ when the submitted patch is 100% correct and ready to ship.
Omega, please update the ui-review flags based on your understanding of this issue. Thank you!
Omega and Carol, please work on the necessary ui-review flag issues here. Thanks!
blocking-b2g: 2.0? → ---
feature-b2g: --- → 2.0
Flags: needinfo?(ofeng)
| Reporter | ||
Comment 15•11 years ago
|
||
Hi Steph,
Sorry for misleading. (Maybe I used the wrong flagging I guess.)
The patch is ui-review+. Since it's already done and ui-review+/review+, I hope it can be landed on 2.0 if there is low risk.
Flags: needinfo?(ofeng)
Comment 16•11 years ago
|
||
No problem, Omega! I just want to be sure everything is actually OK to ship.
Rudy, since this is OK to land (if it is), can you mark this approval?/+ or should it just ride the train to release?
Flags: needinfo?(rlu)
Comment 17•11 years ago
|
||
For me, I would prefer to make this change into the next release, though the patch here may look like a low-risk one.
This is because we modify some of the layouts but not all of them, so I would like to see more testers/users, especially l10n communities, take a look at these changes.
I think this would take some time and if we make this change into v2.0 in a rush, I'm afraid there will no time to make any changes if there is any potential issue.
Please let me know if you don't agree.
Thanks.
Flags: needinfo?(rlu)
Comment 18•11 years ago
|
||
Rudy, that sounds like a good risk assessment. Omega, what will the keyboard look like if it ships? Will it be acceptable or no? If it will be a poor experience, is there something else we could do? Please advise and thank you!
Flags: needinfo?(ofeng)
| Reporter | ||
Comment 19•11 years ago
|
||
It's fine not to land on 2.0.
I'll review all other related layouts and write them down in the UX spec, so that we can have a reference for the next release (2.1).
Flags: needinfo?(ofeng)
Comment 20•11 years ago
|
||
This is not committed in 2.0, removing feature-b2g tag.
feature-b2g: 2.0 → ---
Comment 21•11 years ago
|
||
This has landed, see Comment 12.
Assignee: nobody → ra092767
Status: NEW → RESOLVED
Closed: 11 years ago
status-b2g-v2.1:
--- → fixed
Resolution: --- → FIXED
Updated•11 years ago
|
Priority: -- → P1
Comment 22•11 years ago
|
||
Could you provide a video for me to verify this bug? Thanks.
Flags: needinfo?(ofeng)
Comment 23•11 years ago
|
||
This issue has been verified successfully on Flame v2.1
STR:
1. Launch E-Mail app.
2. New a mail.
3. Tap any email input box to show keyboard.
**There is no '_' key in the second row.
See attachment: verify_video.MP4
Reproducing rate: 0/5
Flame 2.1 versions:
Gaia-Rev dbaf3e31c9ba9c3436e074381744f2971e15c7bf
Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g34_v2_1/rev/ebce587d2194
Build-ID 20141203001205
Version 34.0
Device-Name flame
FW-Release 4.4.2
FW-Incremental eng.cltbld.20141203.034907
FW-Date Wed Dec 3 03:49:18 EST 2014
Bootloader L1TC00011880
You need to log in
before you can comment on or make changes to this bug.
Description
•