Closed Bug 1089092 Opened 11 years ago Closed 10 years ago

[RTL]In the arabic language when you slide right it goes left and vice versa

Categories

(Firefox OS Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: abood.fcb, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.103 Safari/537.36 Steps to reproduce: none Actual results: In the arabic version of the OS when I slide right it goes left and vice versa Expected results: The correction is when I slide right it must go right and vice versa
Group: core-security
Hi Abdelrahman, thank you for your report. Could you let us know which device/version you are using please? Also which application are you referring to? Are you referring to the Task Manager?
Flags: needinfo?(abood.fcb)
Summary: In the arabic language when you slide right it goes left and vice versa → [RTL]In the arabic language when you slide right it goes left and vice versa
it's keon device
Flags: needinfo?(abood.fcb)
Hi Abdelrahman, Could you please let us know which application you are referring to? Are you referring to the Task Manager? As I know, Task Manager does not mirror in RTL. It means Task Manager remains same as that in LTR. And Task Manager is correctly displayed on latest build of Flame 2.2&3.0 and Nexus 5 2.2&3.0 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
QA Whiteboard: [MGSEI-Triage+]
Flags: needinfo?(abood.fcb)
That was in the keon devices.
Flags: needinfo?(abood.fcb)
There's not enough info here to be actionable, and the reporter has not responded with more specifics. FWIW the 2 most likely areas of concern that the bug might be describing - the edge swipe and the task manager - are fixed for RTL in master, see bug 1208170
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
It's an old bug, and I know it has been solved
You need to log in before you can comment on or make changes to this bug.