Closed
Bug 1035986
Opened 10 years ago
Closed 10 years ago
[B2G][2.0][l10n][Calendar] Russian: Add Event title bar text is truncated
Categories
(Mozilla Localizations :: ru / Russian, defect)
Tracking
(b2g-v2.0 affected)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | affected |
People
(Reporter: ckreinbring, Assigned: unghost)
References
Details
(Whiteboard: LocRun2.0)
Attachments
(1 file)
(deleted),
image/png
|
Details |
Description:
The text in the title bar of the Add Event page in the Calendar app is truncated in the Russian language.
Repro Steps:
1) Update a Flame to 20140707000200 and set the device language to Russian.
2) Launch the Calendar app and tap the New Event symbol.
3) Observe the text in the title bar.
Actual:
The Add Event text in the title bar is truncated.
Expected:
The entire text of the Add Event title bar is shown with no errors.
Environmental Variables:
Device: Flame 2.0
Build ID: 20140707000200
Gaia: ef67af27dff3130d41a9139d6ae7ed640c34d922
Gecko: f53099796238
Platform Version: 32.0a2
Firmware Version: v122
See attached screenshot
Reporter | ||
Comment 1•10 years ago
|
||
The title bar of the Add Event page does not show the same string on Flame 1.4
Build ID: 20140707000200
Gaia: 5c9e1e4131d3ac8915ed88b72bb66dc7d97be6a0
Gecko: 2d0c15450488
Platform Version: 30.0
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
Comment 2•10 years ago
|
||
The string was different on 1.4 so please remove the 1.4 tracking flag to avoid confusion.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage-]
Flags: needinfo?(ktucker) → needinfo?(ckreinbring)
Reporter | ||
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage-] → [QAnalyst-Triage?]
status-b2g-v1.4:
unaffected → ---
Flags: needinfo?(ckreinbring) → needinfo?(ktucker)
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Assignee | ||
Comment 3•10 years ago
|
||
Assignee: nobody → unghost
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•