r281259 implemented support for overflow-wrap: anywhere and removed a list of tests that were failing previously. However, some of those tests removed still fail on GTK: Regressions: Unexpected image-only failures (7) imported/w3c/web-platform-tests/css/css-text/overflow-wrap/overflow-wrap-anywhere-009.html [ ImageOnlyFailure ] imported/w3c/web-platform-tests/css/css-text/overflow-wrap/overflow-wrap-anywhere-010.html [ ImageOnlyFailure ] imported/w3c/web-platform-tests/css/css-text/overflow-wrap/overflow-wrap-anywhere-inline-001.html [ ImageOnlyFailure ] imported/w3c/web-platform-tests/css/css-text/overflow-wrap/overflow-wrap-anywhere-inline-002.html [ ImageOnlyFailure ] imported/w3c/web-platform-tests/css/css-text/overflow-wrap/overflow-wrap-anywhere-inline-003.html [ ImageOnlyFailure ] imported/w3c/web-platform-tests/css/css-text/overflow-wrap/overflow-wrap-anywhere-inline-004.html [ ImageOnlyFailure ] imported/w3c/web-platform-tests/css/css-text/overflow-wrap/overflow-wrap-cluster-002.html [ ImageOnlyFailure ] Meanwhile on WPE only 1 fails: Regressions: Unexpected image-only failures (1) imported/w3c/web-platform-tests/css/css-text/overflow-wrap/overflow-wrap-cluster-002.html [ ImageOnlyFailure ]
Looking at the image diffs on GTK <https://people.igalia.com/clopez/wkbug/229347/layout-test-results/results.html> I can see that the real failures there are imported/w3c/web-platform-tests/css/css-text/overflow-wrap/overflow-wrap-anywhere-inline-004.html imported/w3c/web-platform-tests/css/css-text/overflow-wrap/overflow-wrap-cluster-002.html The others look like the usual small-pixel-diffs that make the test fail but in reality is passing The failure on WPE for imported/w3c/web-platform-tests/css/css-text/overflow-wrap/overflow-wrap-cluster-002.html looks the same than on GTK
Expectations updated on r281329
Looks like these failures were a combination of LFC integration not working on GTK and the GTK settings issue in bug 228153 causing problems with the fonts, both of which are now fixed. *** This bug has been marked as a duplicate of bug 228153 ***