Closed Bug 1623813 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 22347 - css-grid: Use documents.font.ready() for tests with Ahem font.

Categories

(Core :: Layout: Grid, task, P4)

task

Tracking

()

RESOLVED FIXED
mozilla76
Tracking Status
firefox76 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 22347 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/22347
Details from upstream follow.

Carlos Alberto Lopez Perez <clopez@igalia.com> wrote:

css-grid: Use documents.font.ready() for tests with Ahem font.

On WebKit based browsers, web-fonts may not be ready when the document.onload signal is triggered, so to avoid flakiness or unexpected failures on the css-grid tests that use the Ahem font this patch changes those tests to start with document.font.ready().

Most of the changes were done in a batch with sed, but there were also some manual edits on the tests below:

css/css-grid/grid-definition/grid-change-fit-content-argument-001.html
css/css-grid/grid-definition/grid-inline-support-grid-template-areas-001.html
css/css-grid/grid-definition/grid-support-grid-template-areas-001.html
css/css-grid/grid-definition/grid-support-repeat-002.html
css/css-grid/grid-items/grid-minimum-size-grid-items-021.html
Component: web-platform-tests → Layout: Grid
Product: Testing → Core
PR 22347 applied with additional changes from upstream: b9888e62e3799d5f91f84cef477a5745469fd570
PR 22347 applied with additional changes from upstream: b9888e62e3799d5f91f84cef477a5745469fd570, 02b166f2be174db6537da8524e97e26bf2bad345
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6ecf4cf5f694
[wpt PR 22347] - css-grid: Use documents.font.ready() for tests with Ahem font., a=testonly
Test result changes from PR not available.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
You need to log in before you can comment on or make changes to this bug.