Closed Bug 387653 Opened 14 years ago Closed 14 years ago
Combining characters positioned wrongly in RTL text
This is the main reason that reftests/bidi/bidi004.html and reftests/bidi/bidi004-j.html are failing on Linux. I'm making it a separate bug blocking bug 386567 rather than attaching the patch there, because there are some other minor issues with positioning that mean that the test still fails even with this fixed.
Assignee: nobody → smontagu
Status: NEW → ASSIGNED
Attachment #271805 - Flags: review?(vladimir)
Attachment #271805 - Flags: review?(vladimir) → review+
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
reftest checked in.
Flags: in-testsuite? → in-testsuite+
The reftest isn't great: it fails on both Windows and Mac, and may start to fail on Linux (or pass on the other platforms) if the default font changes.
Interesting... This relies on the order of glyphs for within each cluster being in reverse-logical order for RTL text. This is contrary to Pango documentation but consistent with pango_ot_buffer_output(). See bug 375864 comment 6. (Fortunately?) Hangul seems to work OK because, with ttf-alee, there is only one glyph per cluster.
(In reply to comment #4) > The reftest isn't great: it fails on both Windows and Mac, and may start to > fail on Linux (or pass on the other platforms) if the default font changes. This bug's reftest (mozilla/layout/reftests/bidi/387653.html) has been failing for clean builds on my Ubuntu Linux box for a while now. (not sure how long, but at least a month, I think) From comment #4, it sounds like this failure was somewhat expected, though... should the test be edited / removed? Here are data-urls for what I'm seeing: test: http://tinyurl.com/3avo8n reference: http://tinyurl.com/22rvbq
I would be OK with removing the test if it's causing problems. layout/reftests/bidi/bidi-006.html is a better test that covers the same issue.
Would it be better to remove the test altogether, or to mark it "random" in the manifest?
I removed it.
You need to log in before you can comment on or make changes to this bug.