Closed Bug 1653434 Opened 4 years ago Closed 4 years ago

[wpt-sync] Sync PR 24638 - Enable FontPreloadingDelaysRendering by default on trunk

Categories

(Core :: Layout: Text and Fonts, task, P4)

Product:
Core
Component:
Layout: Text and Fonts
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla80
Tracking Flags:
Tracking Status
firefox80 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Xiaocheng Hu <xiaochengh@chromium.org> wrote:

Enable FontPreloadingDelaysRendering by default on trunk

According to the finch results on M83 Stable and the discussion, all
launch blockers of this feature have been cleared.

This patch first enables it on trunk. A followup internal CL will enable
it in other channels via finch configurations.

Bug: 1040632
Change-Id: Icd9ab4a85c9d755072310c1be4fc4e524133d6f4
Reviewed-on: https://chromium-review.googlesource.com/2296280
WPT-Export-Revision: 548279224b9f08c7eaa6570b9ddf6e5281cdcf83

Component: web-platform-tests → Layout: Text and Fonts
Product: Testing → Core

CI Results

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

Total 1 tests

Status Summary

Firefox

FAIL: 1

Chrome

FAIL: 1

Safari

FAIL: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

/css/css-fonts/font-display/font-display.html: FAIL (Chrome: FAIL, Safari: FAIL)

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e1ab674573d5
[wpt PR 24638] - Enable FontPreloadingDelaysRendering by default on trunk, a=testonly

https://hg.mozilla.org/mozilla-central/rev/e1ab674573d5

Status: NEW → RESOLVED
Closed: 4 years ago
status-firefox80: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
You need to log in before you can comment on or make changes to this bug.