Closed
Bug 1032946
Opened 12 years ago
Closed 12 years ago
[B2G][2.0][l10n][System] Tamil: Enter PUK code is truncated
Categories
(Mozilla Localizations :: ta / Tamil, defect)
Tracking
(b2g-v2.0 affected)
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| b2g-v2.0 | --- | affected |
People
(Reporter: mclemmons, Unassigned)
References
Details
(Whiteboard: LocRun2.0)
Attachments
(1 file)
|
52.92 KB,
image/png
|
Details |
User enters three incorrect SIM PINs and arrives at the Enter PUK code screen. The header that reads “Enter PUK code” is truncated.
Prerequisites:
1. SIM PIN is enabled in settings.
Repro Steps:
1) Update a Flame to 20140630000201
2) Restart the phone
3) When prompted to enter a SIM PIN, put in the incorrect pin 3 times.
4) Observe device behavior
Actual:
Enter PUK code appears truncated.
Expected:
Enter PUK code does not appear truncated.
Environmental Variables:
Device: Flame 2.0
Build ID: 20140630000201
Gaia: c0c8ad187c0466285f2580531e09f8322996f561
Gecko: d4dc609bcc8a
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: (3/3, 100%)
Link to failed test case: https://moztrap.mozilla.org/manage/case/12106/
See attached: (screenshot – 1 in Tamil)
| Reporter | ||
Comment 1•12 years ago
|
||
This issue does not occur on 1.4 Flame. Tamil was not an available language.
Environmental Variables:
Device: Flame 1.4
BuildID: 20140630000201
Gaia: aa896d5db1b4929f3bf31a0f4bb7de50530222a8
Gecko: 8cba60bc12ef
Version: 30.0 (1.4)
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Updated•12 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Updated•12 years ago
|
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Comment 2•12 years ago
|
||
Corrected in pootle
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•