Closed
Bug 1688168
Opened 3 years ago
Closed 2 years ago
Wrong display of characters of RTL language in a array
Categories
(DevTools :: Console, defect, P3)
DevTools
Console
Tracking
(firefox98 fixed)
RESOLVED
FIXED
98 Branch
Tracking | Status | |
---|---|---|
firefox98 | --- | fixed |
People
(Reporter: calixte, Assigned: Oriol)
References
Details
Attachments
(1 file)
Note the char at position 3 in the array (a shin)
" • תמוז תשע”ז [נז, ד]".split("")
Array(21) [ " ", "•", " ", "ת", "מ", "ו", "ז", " ", "ת", "ש", … ]
expand the array and then see char at position 3 (a tav).
" • תמוז תשע”ז [נז, ד]".split("")
(21) […]
0: " "
1: "•"
2: " "
3: "ת"
4: "מ"
5: "ו"
6: "ז"
7: " "
8: "ת"
9: "ש"
10: "ע"
11: "”"
12: "ז"
13: " "
14: "["
15: "נ"
16: "ז"
17: ","
18: " "
19: "ד"
20: "]"
length: 21
<prototype>: Array []
and " • תמוז תשע”ז [נז, ד]".split("")[3]
shows a tav so I guess that the display of the collapsed array is wrong.
Comment 1•3 years ago
•
|
||
I'm seeing the same thing with Arabic as well
"أهلا".split("")
-> Array(4) [ "أ", "ه", "ل", "ا" ]
inspect("أهلا".split(""))
->
▼ (4) […]
| 0: "أ"
| 1: "ه"
| 2: "ل"
| 3: "ا"
The collapsed array should be ["ا" , "ل", "ه", "أ" ]
Summary: Wrong display of hebrew characters in a array → Wrong display of characters of LTR language in a array
Updated•3 years ago
|
Summary: Wrong display of characters of LTR language in a array → Wrong display of characters of RTL language in a array
Updated•3 years ago
|
Severity: -- → S3
Priority: -- → P3
Assignee | ||
Comment 2•3 years ago
|
||
Something like this?
.objectBox.objectBox-string {
unicode-bidi: isolate;
}
Assignee | ||
Comment 3•2 years ago
|
||
Updated•2 years ago
|
Assignee: nobody → oriol-bugzilla
Status: NEW → ASSIGNED
Pushed by nchevobbe@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/06d8de7f3dda Isolate bidi text in the console. r=nchevobbe
Comment 5•2 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
status-firefox98:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 98 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•