[RTL][Lock Screen]The long LTR contact name is displayed wrong at lockscreen.

RESOLVED WORKSFORME

Status

Firefox OS
Gaia::System::Lockscreen
P2
normal
RESOLVED WORKSFORME
3 years ago
3 years ago

People

(Reporter: Sue, Unassigned)

Tracking

unspecified
ARM
Gonk (Firefox OS)

Firefox Tracking Flags

(b2g-v2.2 affected, b2g-master affected)

Details

Attachments

(3 attachments)

(Reporter)

Description

3 years ago
Created attachment 8601980 [details]
ellipsis of long LTR contacts name in lockscreen.png

[1.Description]:
[RTL][Flame v2.2][Lock Screen]When user receives a call from contact with long LTR name, the ellipses are placed at both sides of long LTR contact name at lockscreen.
See attachment:ellipsis of long LTR contacts name in lockscreen.png

[2.Testing Steps]: 
Prerequisite: Have a contact with a long LTR name.
1. Set system language as Arabic.
2. Lock device.
3. Receive a call from contact with long LTR name.
4. Observe contact name and ellipsis position truncating the text.

[3.Expected Result]: 
4. The ellipsis should be shown at right side of LTR text.

[4.Actual Result]: 
4. The ellipses are placed at both sides of LTR name.

[5.Reproduction build]: 
Device: Flame 2.2 (affected)
Build ID               20150505002501
Gaia Revision          772a9491909abd02dc67278dd453746e2dd358a8
Gaia Date              2015-05-05 02:02:24
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/2df83538ae20
Gecko Version          37.0
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150505.041743
Firmware Date          Tue May  5 04:18:00 EDT 2015
Bootloader             L1TC000118D0

Device: Flame 3.0 (unaffected)
Build ID               20150505010204
Gaia Revision          70077825aab2c7a79611befb40a5fe7e610d5443
Gaia Date              2015-05-04 18:09:33
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/102d0e9aa9e1
Gecko Version          40.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150505.043622
Firmware Date          Tue May  5 04:36:34 EDT 2015
Bootloader             L1TC000118D0

Device: Nexus 5 2.2 (unaffected)
Build ID               20150505002501
Gaia Revision          772a9491909abd02dc67278dd453746e2dd358a8
Gaia Date              2015-05-05 02:02:24
Gecko Revision         https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/2df83538ae20
Gecko Version          37.0
Device Name            hammerhead
Firmware(Release)      5.1
Firmware(Incremental)  eng.cltbld.20150505.041235
Firmware Date          Tue May  5 04:12:53 EDT 2015
Bootloader             HHZ12f

Device: Nexus 5 3.0 (unaffected)
Build ID               20150505160203
Gaia Revision          42dc5f02a9df006b129824cd9bffa93cab937ab2
Gaia Date              2015-05-05 11:06:17
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/5907a8eca521
Gecko Version          40.0a1
Device Name            hammerhead
Firmware(Release)      5.1
Firmware(Incremental)  eng.cltbld.20150505.192812
Firmware Date          Tue May  5 19:28:29 EDT 2015
Bootloader             HHZ12f

[6.Reproduction Frequency]: 
Always Recurrence,5/5

[7.TCID]: 
Free Test
(Reporter)

Updated

3 years ago
QA Whiteboard: [rtl-impact]
status-b2g-v2.2: --- → affected
status-b2g-master: --- → unaffected
(Reporter)

Comment 1

3 years ago
Sorry for confusion in the comment 0, please ignore the Flame 3.0 build version, I have verified the problem on latest build of Flame 3.0 device, and this issue can be repro, the build version is:

Device: Flame 3.0 (affected)
Build ID               20150505160203
Gaia Revision          42dc5f02a9df006b129824cd9bffa93cab937ab2
Gaia Date              2015-05-05 11:06:17
Gecko Revision         https://hg.mozilla.org/mozilla-central/rev/5907a8eca521
Gecko Version          40.0a1
Device Name            flame
Firmware(Release)      4.4.2
Firmware(Incremental)  eng.cltbld.20150505.194217
Firmware Date          Tue May  5 19:42:28 EDT 2015
Bootloader             L1TC000118D0
status-b2g-master: unaffected → affected
(Reporter)

Comment 2

3 years ago
I have tried to repro this issue again on both Flame 3.0 build version in comment 0 and comment 1 by the STRs in comment 0. The build version of Flame 3.0 in comment 0 does not exist this issue, and the build version of Flame 3.0 in comment 1 can repro this issue.
Triage -- P2
Priority: -- → P2

Comment 4

3 years ago
Created attachment 8611082 [details]
verify.png

This issue can not be reproduced on latest build of Flame 2.2&3.0 and Nexus 5 2.2&3.0 by STRs in comment 0.
Result: The ellipsis is shown at right side of long LTR name.
See attachment:verify.png
Rate:0/3

Device information:
Flame 2.2 Build ID: 20150526162504
Flame 3.0 Build ID: 20150526160204
Nexus5 2.2 Build ID: 20150526162504
Nexus5 3.0 Build ID: 20150526160204

Updated

3 years ago
QA Whiteboard: [rtl-impact] → [rtl-impact][MGSEI-Triage+]
Created attachment 8646806 [details]
AriesKK_v2.5.png

Per comment 4, this issue cannot be reproduced on FlameKK 2.2&2.5 and Nexus 5 2.2&2.5 by STRs in comment 0.
And this issue also cannot be reproduced on latest AriesKK v2.5 build, the ellipsis is shown at right side of LTR text.
See attachment:AriesKK_v2.5.png.
Reproducing rate:0/10

Change the status from "New" to "Worksforme", if anyone can repro it, reopen again.

Device info:
AreisKK v2.5 Build ID:20150810201912
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.