Closed Bug 1793010 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 36075 - Line-height should be forced to 'normal' for canvas setFont

Categories

(Core :: DOM: Core & HTML, task, P4)

task

Tracking

()

RESOLVED FIXED
107 Branch
Tracking Status
firefox107 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Rune Lillesveen <futhark@chromium.org> wrote:

Line-height should be forced to 'normal' for canvas setFont

No need to apply line-height as it should end up as 'normal' per spec
anyway[1].

Set the parent style to point to the canvas element to resolve lh units
correctly.

[1] https://html.spec.whatwg.org/multipage/canvas.html#dom-context-2d-font

Bug: 937104
Change-Id: Ib141ca9b5664a896fe86abf2bb25d9d1368e7ffc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3914695
Reviewed-by: Anders Hartvoll Ruud \<andruud@chromium.org>
Commit-Queue: Rune Lillesveen \<futhark@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1051659}

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core

CI Results

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

Total 1 tests and 2 subtests

Status Summary

Firefox

OK : 1
PASS: 1
FAIL: 1

Chrome

OK : 1
PASS: 1
FAIL: 1

Safari

OK : 1
PASS: 1
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/02a97e5661fc [wpt PR 36075] - Line-height should be forced to 'normal' for canvas setFont, a=testonly https://hg.mozilla.org/integration/autoland/rev/ee4c0077bd5b [wpt PR 36075] - Update wpt metadata, a=testonly
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 107 Branch
You need to log in before you can comment on or make changes to this bug.