Closed
Bug 1557667
Opened 5 years ago
Closed 5 years ago
[wpt-sync] Sync PR 17228 - Math script level font size clamping
Categories
(Core :: Layout: Text and Fonts, defect, P4)
Core
Layout: Text and Fonts
Tracking
()
RESOLVED
FIXED
mozilla69
Tracking | Status | |
---|---|---|
firefox69 | --- | fixed |
People
(Reporter: mozilla.org, Unassigned)
References
()
Details
(Whiteboard: [wptsync upstream error])
Sync web-platform-tests PR 17228 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/17228
Details from upstream follow.
Frédéric Wang <fwang@igalia.com> wrote:
Math script level font size clamping
cc @rwlbuis @bkardell @emilio @svgeesus
Assignee | ||
Updated•5 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Comment 1•5 years ago
|
||
PR 17228 applied with additional changes from upstream: 90d09993c72864735e76cf4d5f152436273ffdcd
Assignee | ||
Updated•5 years ago
|
Component: web-platform-tests → Layout: Text and Fonts
Product: Testing → Core
Assignee | ||
Updated•5 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Comment 2•5 years ago
|
||
Pushed to try https://treeherder.mozilla.org/#/jobs?repo=try&revision=3f326e784ae411e599c3b7cf2d6593e2859f6808
Assignee | ||
Updated•5 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Assignee | ||
Updated•5 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync downstream]
Assignee | ||
Updated•5 years ago
|
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Pushed by james@hoppipolla.co.uk: https://hg.mozilla.org/integration/mozilla-inbound/rev/a940827f4bb0 [wpt PR 17228] - Math script level font size clamping, a=testonly
Comment 4•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox69:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
Assignee | ||
Updated•5 years ago
|
Whiteboard: [wptsync downstream error] → [wptsync upstream error]
You need to log in
before you can comment on or make changes to this bug.
Description
•