Closed Bug 1615682 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 21807 - Migrate font-display to document policy

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox76 fixed)

RESOLVED FIXED
mozilla76
Tracking Status
firefox76 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Charlie Hu <chenleihu@google.com> wrote:

Migrate font-display to document policy

This CL migrates font-display from feature policy to document policy.

Bug: 993790
Change-Id: Id4c822e0a42594ab75919819e4f1b78ca6a263f3
Reviewed-on: https://chromium-review.googlesource.com/2036518
WPT-Export-Revision: 6b43c58e2c0121238c18f1b47ec5dbc66b4d18e8

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 2 tests and 1 subtests

Status Summary

Firefox

TIMEOUT: 2
NOTRUN : 2

Chrome

TIMEOUT: 2
NOTRUN : 2

Safari

ERROR : 2
NOTRUN : 2

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/document-policy/font-display/font-display-document-policy-reporting.tentative.html: TIMEOUT (Chrome: TIMEOUT, Safari: ERROR)
font-display-late-swap Report Format: NOTRUN (Chrome: NOTRUN, Safari: NOTRUN)
/document-policy/font-display/font-display-document-policy-report-only.tentative.html: TIMEOUT (Chrome: TIMEOUT, Safari: ERROR)
font-display-late-swap Report Format: NOTRUN (Chrome: NOTRUN, Safari: NOTRUN)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/a932cf579ae2
[wpt PR 21807] - Migrate font-display to document policy, a=testonly
https://hg.mozilla.org/integration/autoland/rev/c46f152dd272
[wpt PR 21807] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla76
Regressions: 1621954
You need to log in before you can comment on or make changes to this bug.