[B2G][2.0][l10n][Settings] Serbian Latin: 'New voicemail message' notification is truncated

RESOLVED FIXED

Status

RESOLVED FIXED
5 years ago
5 years ago

People

(Reporter: rpribble, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-v1.4 fixed, b2g-v2.0 fixed)

Details

(Whiteboard: [2.0-exploratory], [l10n])

Attachments

(1 attachment)

(Reporter)

Description

5 years ago
Created attachment 8473354 [details]
Screenshot.png

Description:
The 'New voicemail message' notification is truncated in the pull down menu, appearing as '(SIM 1) Jedna nova govorna p...'. If the user has more than one voicemail [ex: '(SIM 1) 2 nove govorne poruke'], the string does not appear truncated.

Repro Steps:
1) Update a Flame device to BuildID: 20140811000210
2) Receive one new voicemail
3) Pull down the notifications menu
  
Actual:
The 'New voicemail message' notification is truncated.
  
Expected: 
No unintended truncations occur.
  
Environmental Variables:
Device: Flame 2.0 (319MB)
BuildID: 20140811000210
Gaia: de28796a8956a48bb98ca67df6a33e0622d642d1
Gecko: 5256345f62bd
Version: 32.0 (2.0)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
  
Notes:
  
Repro frequency: 100%
See attached: Screenshot

----------------------------------------

This issue also occurs on the Flame v1.4 (319MB).

Device: Flame 1.4
BuildID: 20140813063003
Gaia: 5bb0edb3446df787c48dbb37272827ad94cb9245
Gecko: 3d30ba3dc503
Version: 30.0 (1.4)
Firmware: V123
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

The string appears as '(SIM 1) Jedna nova govorna...'.
(Reporter)

Updated

5 years ago
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][lead-review+]
Closing this one.

Please verify that the problem has been fixed.
Thanks.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
status-b2g-v1.4: affected → fixed
status-b2g-v2.0: affected → fixed
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.