Closed
Bug 1033870
Opened 10 years ago
Closed 10 years ago
[B2G][2.0][l10n][Settings][Developer] Swahili: The string "App Memory" and "Frame per second" on Developer menu are truncated.
Categories
(Mozilla Localizations :: sw / Swahili, defect)
Tracking
(b2g-v2.0 affected)
RESOLVED
DUPLICATE
of bug 1033583
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | affected |
People
(Reporter: ychung, Unassigned)
References
Details
(Whiteboard: LocRun2.0)
Attachments
(1 file)
(deleted),
image/png
|
Details |
Description: On the Developer HUD screen on Settings > Developer, the string "App Memory" and "Frame per second" are truncated. Repro Steps: 1) Update a Flame to BuildID: 20140630000201. 2) Set the device language as Swahili. 3) Navigate to Settings > Developer > Developer HUD. 4) Observe the string "App Memory" and "Frame per second" on the menu. Actual: The string "App Memory" and "Frame per second" are truncated in Swahili. Expected: The string "App Memory" and "Frame per second" are NOT truncated in Swahili. Environmental Variables: Device: Flame 2.0 BuildID: 20140702000201 Gaia: 3bfe47c58c959c42f5ffe0309b5380ea514ccd69 Gecko: f40e767ea283 Version: 32.0a2 (2.0) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Repro Frequency: 100% Link to failed test case: https://moztrap.mozilla.org/manage/case/12508/ https://moztrap.mozilla.org/manage/case/12611/ See attached screenshot
Reporter | ||
Comment 1•10 years ago
|
||
This issue does not occur on 1.4 Flame. Environmental Variables: Device: Flame 1.4 Build ID: 20140702063007 Gaia: e8599c2b346addf3bf857310502e5b542ae7d0b2 Gecko: 5ff8eb391b65 Version: 30.0 (1.4) Firmware Version: v122 User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Swahili was not an available language.
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•