New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecate/Remove the <mstyle>
element
#181
Comments
I'm generally in favor of this proposal ( for the same "simpler is better" principle as with #173 ). If the original features intended for I am not sure if there are good arguments for retaining it in MathML Full, and if there is desire to allow an option for third-party rendering independent of CSS. If not, deprecation there sounds reasonable as well. That said, there is a pending "twist" to the story. We have an ongoing internal discussion about repurposing The basis for reuse was that the group thought leveraging an existing element is easier both technically and politically, compared to inventing a new one (and seeking support for addition into Core). But if that discussion doesn't gain traction, |
I suppose one could consider allowing all of those attributes on I wasn't aware or had forgotten that In summary, I'd like to hear why "overloading" |
In MathML <= 3, the idea of mstyle was to change the default value of attributes but it had several issues (e.g. having to deal conflicting attribute names, mathbackground originally not applied to the actual element, not really corresponding to actual CSS "style"). In MathML Core, the idea is instead to rely on CSS for styling. Ideally, all stylistic features should correspond to CSS properties and attributes would just mapped to style as presentational hints. This is unfortunately not possible for MathML features depending on the DOM content (operator dict and all) but at least the global ones are currently handled. Regarding Anyway, coming back to the actual issue, we can either remove |
The children of a top-level <mfrac>
<mstyle mathcolor="red">
<mi>x</mi>
<mo>+</mo>
<mi>y</mi>
</mstyle>
<mstyle mathcolor="green">
<mi>y</mi>
<mo>+</mo>
<mi>z</mi>
</mstyle>
</mfrac> compare that to the equivalent: <mfrac>
<mrow style="color:red;">
<mi>x</mi>
<mo>+</mo>
<mi>y</mi>
</mrow>
<mrow style="color:green;">
<mi>y</mi>
<mo>+</mo>
<mi>z</mi>
</mrow>
</mfrac> To my current thinking, a good direction of long-term reconciliation with HTML is to increasingly think of an "mrow" element as a "math-y version of a span". |
Currently, it's strictly equivalent to the
<mrow>
element for layout purpose.Similarly to what was @dginev proposed in #173 we probably want to remove the
<mstyle>
element from MathML Core and deprecate it from MathML Full.The text was updated successfully, but these errors were encountered: