Closed
Bug 1035926
Opened 10 years ago
Closed 10 years ago
[B2G][l10n][2.0][Facebook] Spanish: "Welcome to Facebook" appears truncated when attempting to sync contacts
Categories
(Mozilla Localizations :: es-ES / Spanish, defect)
Tracking
(b2g-v2.0 affected)
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | affected |
People
(Reporter: rkunkel, Assigned: rpmdisguise-nave)
References
Details
(Whiteboard: LocRun2.0)
Attachments
(1 file)
(deleted),
image/png
|
Details |
Description:
When the user has set their device to Spanish and attempts to sync their Facebook friends, "Welcome to Facebook" header appears truncated
Setup Steps:
1) Settings > Language > Spanish
Repro Steps:
1) Update a Flame device to BuildID: 20140707000200
2) Enable Data or connect to WiFi
3) Contacts > Settings > 'Sync friends'
4) Select Espanol if not auto-selected
Actual:
"Welcome to Facebook" header appears truncated
Expected:
Translated strings do not appear truncated
Environmental Variables:
Device: Flame 2.0
BuildID: 20140707000200
Gaia: ef67af27dff3130d41a9139d6ae7ed640c34d922
Gecko: f53099796238
Version: 32.0a2
Firmware Version: v122
2.0 - 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/12798/
See attached: screenshot
Reporter | ||
Comment 1•10 years ago
|
||
This issue does not occur on the 1.4 Branch
Environmental Variables:
Device: Flame 1.4
BuildID: 20140707000200
Gaia: 5c9e1e4131d3ac8915ed88b72bb66dc7d97be6a0
Gecko: 2d0c15450488
Version: 30.0
Firmware Version: v122
1.4 - Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
This string was introduced in 2.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
Comment 2•10 years ago
|
||
I would say that this is Facebook's own site title, so nothing we can do.
https://m.facebook.com/
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Updated•10 years ago
|
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
You need to log in
before you can comment on or make changes to this bug.
Description
•