You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However there does not seem to one here and the current draft is silent on the issue.
MathML specifies that white space at start and end of token elements is ignored (essentially like whitespace at ends of a HTML <p>) Almost all examples in the current MathML4 draft have space in token elements that needs to be removed while rendering.
<mfrac linethickness="3px">
<mrow>
<mo> ( </mo>
<mfrac linethickness="0">
<mi> a </mi>
<mi> b </mi>
</mfrac>
<mo> ) </mo>
<mfrac>
<mi> a </mi>
<mi> b </mi>
</mfrac>
</mrow>
<mfrac>
<mi> c </mi>
<mi> d </mi>
</mfrac>
</mfrac>
Renders in Firefox as
The rendering in Edge is
in which the variables are not italic and the space is affecting the spacing. If the space characters are deleted, edge renders this as
MathML Core should mandate the firefox behaviour here, for compatibility with the existing corpus of MathML documents and for general usability and user expectations.
The text was updated successfully, but these errors were encountered:
There is a related issue in the repo for the full spec#165
However there does not seem to one here and the current draft is silent on the issue.MathML specifies that white space at start and end of token elements is ignored (essentially like whitespace at ends of a HTML
<p>
) Almost all examples in the current MathML4 draft have space in token elements that needs to be removed while rendering.For example
https://w3c.github.io/mathml/#examples-5
Renders in Firefox as
The rendering in Edge is
in which the variables are not italic and the space is affecting the spacing. If the space characters are deleted, edge renders this as
MathML Core should mandate the firefox behaviour here, for compatibility with the existing corpus of MathML documents and for general usability and user expectations.
The text was updated successfully, but these errors were encountered: