Closed Bug 1934244 Opened 1 year ago Closed 1 year ago

[wpt-sync] Sync PR 49441 - Fix crash during serialization of the font shorthand.

Categories

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

task

Tracking

()

RESOLVED FIXED
135 Branch
Tracking Status
firefox135 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Steinar H. Gunderson <sesse@chromium.org> wrote:

Fix crash during serialization of the font shorthand.

It's not clear whether calc() expressions should be converted into
font keywords; not doing it seems like the most consistent handling,
given that calc() is never converted into literals anywhere else,
but it clashes with existing practice.

Bug: 40946458
Change-Id: I60c4fa354ec016ceeb872b7dabbef14d69412814
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6057817
Commit-Queue: Steinar H Gunderson \<sesse@chromium.org>
Reviewed-by: Anders Hartvoll Ruud \<andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1389776}

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

CI Results

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

Total 1 tests and 4 subtests

Status Summary

Firefox

OK : 1
PASS: 3
FAIL: 1

Chrome

OK : 1
PASS: 3
FAIL: 1

Safari

OK : 1
PASS: 3
FAIL: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/d3fb681e5551 [wpt PR 49441] - Fix crash during serialization of the font shorthand., a=testonly https://hg.mozilla.org/integration/autoland/rev/b7c60abebb73 [wpt PR 49441] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 135 Branch
You need to log in before you can comment on or make changes to this bug.