In T346795#9246729, @Dpcarlisle wrote:Firefox reports several parse errors in the mathml in
https://en.wikipedia.beta.wmflabs.org/wiki/Help:MathTestNative
Error in parsing the value '' for 'columnspacing' attribute of <mtable/>. Attribute ignored.Invalid markup: Incorrect number of children for <munder/> tag. Help:MathTestNative Invalid markup: Incorrect number of children for <msup/> tag. Help:MathTestNative Invalid markup: Incorrect number of children for <munder/> tag. Help:MathTestNative Invalid markup: Incorrect number of children for <msup/> tag. Help:MathTestNative Invalid markup: Incorrect number of children for <munder/> tag. node.js:370:30 Invalid markup: Incorrect number of children for <msup/> tag. node.js:370:30 Invalid markup: Incorrect number of children for <munder/> tag. node.js:370:30 Invalid markup: Incorrect number of children for <msup/> tag. node.js:370:30 Invalid markup: Incorrect number of children for <munder/> tag. utils.js:166:21A typical cause of the incorrect child count is empty tex groups.
For example the slightly nonsensical example
\underset{\mathrm{def}}{}on the page is producing an <munder> with just one child. The mathml could be simplified simply removing the munder (corresponding to correcting the tex to \mathrm{def} without the spurious \underset) or if you want to model the tex exactly you need an empty <mrow/> (or <mi/> to match the empty tex argument so that <munder> has two children.
Description
Description
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Declined | Stegmujo | T310373 Make Mathoid Client a standalone class | |||
Open | None | T327098 Implement Math Accessibility Features necessary for Intent attribute usage | |||
Resolved | Physikerwelt | T302628 Implement native MathML rendering in Math | |||
Resolved | Physikerwelt | T346795 User Feedback to MathML implementation in Math extension | |||
Resolved | Physikerwelt | T355999 native: Check debug console on Help:MathTestNative | |||
Resolved | Physikerwelt | T357343 Incorrect mo in \sin \log_a |
Event Timeline
Comment Actions
The number of errors is reduced
Invalid markup: Incorrect number of children for <msub/> tag. Help:MathTestNative Invalid markup: Incorrect number of children for <msub/> tag. Help:MathTestNative Invalid markup: Incorrect number of children for <msub/> tag. 2 layout.js:317:44
Comment Actions
At least one of the cases is related to a bug in muder / mover, already fixed in https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Math/+/993233. Let's recheck once the change is merged.
Comment Actions
Also there is one warning “mathvariant='double-struck'” on MathML elements is deprecated and will be removed at a future date. which can be a problem for chrome rendering.
Comment Actions
And one more message
Support for rendering stretched MathML operators with STIXGeneral fonts is deprecated and may be removed at a future date. For details about newer fonts that will continue to be supported, see https://developer.mozilla.org/docs/Mozilla/MathML_Project/Fonts
Not sure where this comes from
Comment Actions
Now only warning about deprecated elements and entirely unrelated cookie problems remain:
Some cookies are misusing the recommended “SameSite“ attribute 25 “mathvariant='fraktur'” on MathML elements is deprecated and will be removed at a future date. Help:MathTestNative Support for rendering stretched MathML operators with STIXGeneral fonts is deprecated and may be removed at a future date. For details about newer fonts that will continue to be supported, see https://developer.mozilla.org/docs/Mozilla/MathML_Project/Fonts