Open Bug 1846930 Opened 1 year ago Updated 1 year ago

Test semantics-4.html is failing after bug 1588733

Categories

(Core :: MathML, defect)

defect

Tracking

()

Tracking Status
firefox-esr102 --- unaffected
firefox-esr115 --- wontfix
firefox116 --- wontfix
firefox117 --- wontfix
firefox118 --- fix-optional

People

(Reporter: fredw, Assigned: fredw)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: regression)

The original testcase from bug 1131000 was to make

<math display="block" xmlns="http://www.w3.org/1998/Math/MathML">
<semantics>
<mtable width="100%" mathbackground="red">
<mtr> <mtd><mi>x</mi></mtd> </mtr>
</mtable>
<annotation encoding="application/x-tex">x</annotation>
</semantics>
</math>

render with same width as

<math display="block" xmlns="http://www.w3.org/1998/Math/MathML">
<mtable width="100%" mathbackground="red">
<mtr> <mtd><mi>x</mi></mtd> </mtr>
</mtable>
<annotation encoding="application/x-tex">x</annotation>
</math>

However, the patch for bug 1131000 only fixed a very particular case for <semantics>/<maction> elements not for other elements (e.g. <mrow>, <mpadded>, etc). After bug 1588733, these elements behave like <mrow>s and so the testcase regressed.

In bug 1788223, I tweaked the testcase to wrap the reference to wrap the table in an <mrow> but didn't realize it's actually changing the purpose the test, so I'll restore the original testcase and mark it as failing.

We need to check what MathML Core says, in particular there are many tests related to CSS width/height that Firefox currently fails (and Chrome passes) and some text in the spec which would probably give a more general answer to the problem.

As a side note, the testcase uses the attribute mtable@width which is not part of MathML Core (https://w3c.github.io/mathml/#presm_mtable_attrs) but we essentially map it to the width property ( https://searchfox.org/mozilla-central/rev/cb045e3330e3fa479c5568c738a770ac5b3efe2a/dom/mathml/MathMLElement.cpp#366 ).

Set release status flags based on info from the regressing bug 1588733

You need to log in before you can comment on or make changes to this bug.