RESOLVED FIXED 212205
[WPE] fast/text/zero-width-characters.html, fast/text/zero-width-characters-complex-script.html failing
https://bugs.webkit.org/show_bug.cgi?id=212205
Summary [WPE] fast/text/zero-width-characters.html, fast/text/zero-width-characters-c...
Zan Dobersek
Reported 2020-05-21 05:34:48 PDT
The following two zero-width-character tests are failing on WPE since being enabled: - fast/text/zero-width-characters.html - fast/text/zero-width-characters-complex-script.html --- /app/webkit/WebKitBuild/Release/layout-test-results/fast/text/zero-width-characters-expected.txt +++ /app/webkit/WebKitBuild/Release/layout-test-results/fast/text/zero-width-characters-actual.txt @@ -1,3 +1,3 @@ This test checks various characters that should always be zero width to ensure that they are. The WebKit text system ensures this in a way that's independent of the fonts installed on the system. -PASS: All the characters had zero width. +FAIL: One or more of the characters had a non-zero width. --- /app/webkit/WebKitBuild/Release/layout-test-results/fast/text/zero-width-characters-complex-script-expected.txt +++ /app/webkit/WebKitBuild/Release/layout-test-results/fast/text/zero-width-characters-complex-script-actual.txt @@ -1,3 +1,3 @@ This test checks various characters that should always be zero width to ensure that they are when enclosed by complex script characters. The WebKit text system ensures this in a way that's independent of the fonts installed on the system. -PASS: All characters had zero-width. +FAIL: 1 characters had non-zero width or failed to get measured when test with Devanagari
Attachments
Diego Pino
Comment 1 2022-01-12 23:15:40 PST
These two tests were fixed somewhere in between [r281383-r281389] and have been passing consistently since then: https://results.webkit.org/?platform=WPE&suite=layout-tests&suite=layout-tests&test=fast%2Ftext%2Fzero-width-characters.html&test=fast%2Ftext%2Fzero-width-characters-complex-script.html Removed test failures from test expectations in r287972. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.