Closed
Bug 978289
Opened 10 years ago
Closed 10 years ago
[B2G][Keyboard] The R$ special character is missing from the keyboard
Categories
(Firefox OS Graveyard :: Gaia::Keyboard, defect)
Tracking
(b2g-v1.3 unaffected, b2g-v1.4 affected)
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
b2g-v1.3 | --- | unaffected |
b2g-v1.4 | --- | affected |
People
(Reporter: jharvey, Unassigned)
References
Details
(Keywords: regression, Whiteboard: burirun1.4-1)
Description: When the user holds the "R" key on the keyboard the special character "R$" does not appear. This is inconsistent with previous builds and some language's keyboards where this character is available. Repro Steps: 1) Updated Buri to BuildID: 20140227040202 2) Select Messages app. 3) Select the new message icon. 4) Open the keyboard and hold the R button. Actual: No special characters appear. Expected: The special character "R$" is available. Environmental Variables: Device: Buri v1.4 Mozilla BuildID: 20140227040202 Gaia: 22d48b62df7901ad45044f66e15e7d8943884a06 Gecko: a98a1d78817f Version: 30.0a1 Firmware Version: v1.2-device.cfg Notes: Repro frequency: 100% Link to failed test case: https://moztrap.mozilla.org/manage/case/6450/
This issue does not reproduce on Buri 1.3 1.3 Environmental Variables: Device: Buri 1.3 BuildID: 20140228004002 Gaia: 9e439c98a05bde90b571701ef0b2dbb4249ef196 Gecko: 7fb42ba60248 Version: 28.0 Firmware Version: v1.2-device.cfg
status-b2g-v1.3:
--- → unaffected
status-b2g-v1.4:
--- → affected
Updated•10 years ago
|
blocking-b2g: --- → 1.4?
Keywords: regression,
regressionwindow-wanted
Comment 2•10 years ago
|
||
This was changed by the following 2 bugs, which I add dependency for. Hi jharvey, Could you please clarify if this is for English or for any specific languages? What is the main concern of removing "R$" from non-pt-BR language? If there is any, I guess we could ask for UX/l10n team input here. Thanks.
Updated•10 years ago
|
Keywords: regressionwindow-wanted
Comment 3•10 years ago
|
||
(In reply to Rudy Lu [:rudyl] from comment #2) > > Could you please clarify if this is for English or for any specific > languages? This is an English only test run, so this is likely English specifically. > What is the main concern of removing "R$" from non-pt-BR language? If there > is any, I guess we could ask for UX/l10n team input here. I think the reverse of that question needs to be analyzed here - why is this no longer needed? Is UX in agreement with the change? Can't exactly tell by the bug discussion on the rationale. Leaving needinfo on UX to see what they think as well. Going to clear the nom for now until we get a better understanding of what the right direction is.
blocking-b2g: 1.4? → ---
Flags: needinfo?(jharvey) → needinfo?(firefoxos-ux-bugzilla)
Comment 4•10 years ago
|
||
Flagging Carrie on keyboard UX.
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(cawang)
Comment 5•10 years ago
|
||
I don't think we've decided to remove R$ from the R key. Is there any reason that we shall remove it? Thank.
Flags: needinfo?(cawang)
Comment 6•10 years ago
|
||
Rudy - Can you sync up with Carrie and come to a conclusion of whether we should keep or remove the R$ from the R key?
Flags: needinfo?(rlu)
Comment 7•10 years ago
|
||
I don't have a strong opinion on this and I don't see any clear rationale behind this change either, from bug 943812. My understanding for this change is, since we have pt-BR (Portuguese) layout, and it can serve to input "R$", then there is no need to put "R$" in all other language. If you need that, you could just enable pt-BR keyboard and get that. If we reference Android phone, you could see that, "R$" is not an alternative character for "R" in English layout. Carrie, If you agree on the above, then I guess we could close this bug? Thanks.
Flags: needinfo?(rlu) → needinfo?(cawang)
Comment 8•10 years ago
|
||
OK then, I'm fine with removing the "R$" key. Thanks for the clarification. :)
Flags: needinfo?(cawang)
Comment 9•10 years ago
|
||
Carrie, Thanks, then I'll just dupe this one to the bug that made this change.
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.
Description
•