Bug 206265 - [GTK] WPT tests css/css-multicol/multicol-rule-fraction-003.xht and css/css-multicol/multicol-rule-shorthand-2.xht fail
Summary: [GTK] WPT tests css/css-multicol/multicol-rule-fraction-003.xht and css/css-m...
Status: RESOLVED INVALID
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-14 16:05 PST by Carlos Alberto Lopez Perez
Modified: 2020-01-15 06:26 PST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carlos Alberto Lopez Perez 2020-01-14 16:05:30 PST
The following two tests:

  imported/w3c/web-platform-tests/css/css-multicol/multicol-rule-fraction-003.xht [ ImageOnlyFailure ]
  imported/w3c/web-platform-tests/css/css-multicol/multicol-rule-shorthand-2.xht [ ImageOnlyFailure ]

were failing on platform GTK before bug 204671 because we were antialiasing Ahem.

However, after disabling antialiasing for the Ahem font in bug 204671 they continue to fail.

Looking at the visual diff, it pretty much appears we are still antialiasing Ahem for this two tests.

Its unclear why it happens, but it looks something related in the way we run this tests in our runner
As I can't reproduce the failure running the tests with the WPT runner.
I can't also reproduce the antialiasing issue in the MiniBrowser, only seems to happen with WTR.
Comment 1 Carlos Alberto Lopez Perez 2020-01-14 17:30:36 PST
This seems to be caused because we are disabling gtk-xft-hinting in WTR.
Comment 2 Carlos Alberto Lopez Perez 2020-01-15 06:26:22 PST
(In reply to Carlos Alberto Lopez Perez from comment #1)
> This seems to be caused because we are disabling gtk-xft-hinting in WTR.

Seems I got confused with this. Enabling hinting was workarounding the issue maybe. The underlying cause was that this two tests loaded the Ahem font as a webfont, and that was not working when i tested this on a previous version of the patch from bug 204671