Closed
Bug 976791
Opened 10 years ago
Closed 10 years ago
[B2G][Keyboard] Portuguese: '#' not available on the Portuguese keyboard
Categories
(Firefox OS Graveyard :: Gaia::Keyboard, defect)
Tracking
(blocking-b2g:1.3+, b2g-v1.2 unaffected, b2g-v1.3 fixed, b2g-v1.3T fixed, b2g-v1.4 fixed)
Tracking | Status | |
---|---|---|
b2g-v1.2 | --- | unaffected |
b2g-v1.3 | --- | fixed |
b2g-v1.3T | --- | fixed |
b2g-v1.4 | --- | fixed |
People
(Reporter: rkunkel, Assigned: reuben)
References
Details
(Keywords: l12y, regression, Whiteboard: LocRun1.3, [systemsfe])
Attachments
(2 files)
47.80 KB,
image/png
|
Details | |
46 bytes,
text/x-github-pull-request
|
djf
:
review+
fabrice
:
approval-gaia-v1.3+
|
Details | Review |
Description: When the device's language is set to Portuguese and it's keyboard is set to Portuguese, the '#' key will not be available to the user Repro Steps: 1) Update Buri to v1.3 BuildID: 20140220004002 2) Open the Message app 3) Begin a new message 4) Try and type the '#' key Actual: The '#' key is not available to the Portuguese keyboard Expected: For the '#' to be available to the Portuguese keyboard Environmental Variables: Device: Buri 1.2 MOZ BuildID: 20140220004002 Gaia: 539a25e1887b902b8b25038c547048e691bd97f6 Gecko: 2ea6a65eea23 Version: 26.0 Firmware Version: V1.2-device.cfg Repro frequency: 100% Link to failed test case: See attached: Screenshots
Reporter | ||
Updated•10 years ago
|
Comment 1•10 years ago
|
||
Adding David and Kevin to this bug Nominating as this seems pretty bad
blocking-b2g: --- → 1.3?
Summary: [B2G][1.3][Keyboard] Portuguese: '#' not available on the Portuguese keyboard → [B2G][Keyboard] Portuguese: '#' not available on the Portuguese keyboard
Updated•10 years ago
|
Component: pt-BR / Portuguese (Brazil) → Gaia::Keyboard
Product: Mozilla Localizations → Firefox OS
Comment 2•10 years ago
|
||
This regression was caused by bug 936565, which remove symbol layout page of Portuguese, so it would fallback to use the default one, and the default one does not have '#' character.
Blocks: 936565
Assignee | ||
Comment 3•10 years ago
|
||
I don't get it. We inherit the symbol layout from en-US, which does have the '#' symbol. I can't reproduce this bug, on my phone I get the same symbol layout as the English keyboard.
Assignee | ||
Comment 4•10 years ago
|
||
Nevermind, for some reason just switching the language to pt-BR in Settings wasn't enough.
Assignee | ||
Comment 5•10 years ago
|
||
Comment 6•10 years ago
|
||
Comment on attachment 8382400 [details] [review] Some adjustments to the pt-BR layout Reuben, It looks like you're just making the alternates layout in pt_br follow the layout in en_us, exept that $ becomes R$, and you aren't putting the comma and period around the spacebar. If those are the changes you're making, it would be helpful to say so instead of just "some adjustments". The changes seem fine to me. I've marked one nit on Github. I don't feel that I've got authority to authorize this sort of localization change. Delphine, is this something you can sign off on?
Attachment #8382400 -
Flags: review?(dflanagan) → review+
Assignee | ||
Comment 8•10 years ago
|
||
For clarification: I changed the symbols layout to match the en-US keyboard. The locale differences in the main layout (` before ˆ before ´ before ¨, ç before ć, etc) remain there. David, thanks for the review. I've addressed the nits and will update the commit message. FWIW, I feel like the layouts should be in the l10n repos.
Comment 9•10 years ago
|
||
Note: this is a regression, can we have this 1.3+ed please?
Comment 10•10 years ago
|
||
Reuben being a key contributor of ours in Brazil, I think he's best suited to make the call here on the layout. Side comment, I strongly believe that keyboard layouts should not be part of the l10n repos. I think it's good that the keyboard selection is independent from the UI locale set selection.
Flags: needinfo?(l10n)
Updated•10 years ago
|
blocking-b2g: 1.3? → 1.3+
Assignee | ||
Comment 11•10 years ago
|
||
Merged: https://github.com/mozilla-b2g/gaia/commit/0385d529cc3e71c1f82db9bf71351b578a48dbce
Assignee | ||
Updated•10 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 12•10 years ago
|
||
Comment on attachment 8382400 [details] [review] Some adjustments to the pt-BR layout [Approval Request Comment] [Bug caused by] (feature/regressing bug #): Bug 936565 [User impact] if declined: '#' not available in the keyboard [Testing completed]: Manual testing, passes Travis [Risk to taking this patch] (and alternatives if risky): Low [String changes made]: None
Attachment #8382400 -
Flags: approval-gaia-v1.3?
Updated•10 years ago
|
Attachment #8382400 -
Flags: approval-gaia-v1.3? → approval-gaia-v1.3+
Updated•10 years ago
|
Whiteboard: LocRun1.3 → LocRun1.3, [systemsfe]
Target Milestone: --- → 1.4 S2 (28feb)
Comment 13•10 years ago
|
||
v1.3: dbb2f0390fe8f8158ce27103207987770cfd0f59
status-b2g-v1.4:
--- → fixed
Assignee | ||
Comment 14•10 years ago
|
||
(In reply to Axel Hecht [:Pike] from comment #10) > Side comment, I strongly believe that keyboard layouts should not be part of > the l10n repos. I think it's good that the keyboard selection is independent > from the UI locale set selection. I also think that's a good thing. Why would putting the keyboard layout in the locale repo change anything about it?
Comment 15•10 years ago
|
||
(In reply to Reuben Morais [:reuben] from comment #14) > I also think that's a good thing. Why would putting the keyboard layout in > the locale repo change anything about it? You can't ship the keyboard if you don't ship that specific locale (or at least that's how I see it).
Updated•10 years ago
|
status-b2g-v1.3T:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•