Closed
Bug 1572213
Opened 7 years ago
Closed 7 years ago
[wpt-sync] Sync PR 18323 - mfrac without bar: Remove test for AxisHeight parameter.
Categories
(Core :: MathML, task, P4)
Core
MathML
Tracking
()
RESOLVED
FIXED
mozilla70
| Tracking | Status | |
|---|---|---|
| firefox70 | --- | fixed |
People
(Reporter: wpt-sync, Unassigned)
References
()
Details
(Whiteboard: [wptsync downstream])
Sync web-platform-tests PR 18323 into mozilla-central (this bug is closed when the sync is complete).
PR: https://github.com/web-platform-tests/wpt/pull/18323
Details from upstream follow.
Frédéric Wang <fwang@igalia.com> wrote:
mfrac without bar: Remove test for AxisHeight parameter.
AxisHeight is no longer involved in the layout:
https://mathml-refresh.github.io/mathml-core/#fraction-with-zero-line-thicknessConfirmed by Microsoft:
https://lists.w3.org/Archives/Public/public-mathml4/2019Aug/0019.html
| Assignee | ||
Comment 1•7 years ago
|
||
PR 18323 applied with additional changes from upstream: 67aa02fa5eece637bf8ed99f0e3e3f52f1b0aa72
| Assignee | ||
Updated•7 years ago
|
Component: web-platform-tests → MathML
Product: Testing → Core
| Assignee | ||
Comment 2•7 years ago
|
||
| Assignee | ||
Comment 3•7 years ago
|
||
Pushed to try (stability) https://treeherder.mozilla.org/#/jobs?repo=try&revision=f59649bf6835a0d6812790cfeb924496442d411a
| Assignee | ||
Comment 4•7 years ago
|
||
Ran 1 tests and 6 subtests
OK : 1
PASS : 2
FAIL : 4
Existing tests that now have a worse result (e.g. they used to PASS and now FAIL):
/mathml/presentation-markup/fractions/frac-parameters-2.html
BottomDisplayStyleShiftDown: FAIL
BottomShiftDown: FAIL
ToShiftUp: FAIL
TopDisplayStyleShiftUp: FAIL
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/a4e156a747af
[wpt PR 18323] - mfrac without bar: Remove test for AxisHeight parameter., a=testonly
Comment 6•7 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox70:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
You need to log in
before you can comment on or make changes to this bug.
Description
•