-
Notifications
You must be signed in to change notification settings - Fork 14
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
Consider adding menclose to core #245
Comments
Note: It references mathml full #105, not the auto-linked 105 in this same (mathml-core) repo |
This recently came up in a discussion about MathML support in mathlive. If you look at the differences between Core and MathML 3, the ones that aren't easy to have work in both are:
The first two are not widely implemented, so from a practical point of view, the difference is not a big deal when deciding what to generate. Getting css support into the other browsers would be great, but isn't simple. That leaves supporting Prioritizing adding |
Polyfills and IntentA new consideration we will have with MathML 4 will be whether polyfills can/should use the new Neil's example polyfill recovery for <mrow class="menclose" intent="enclose(up-right-diagonal-strike, $content)">
<mrow arg="content">...</mrow>
<mrow class="menclose-arrow" style="..."><mrow class="line"></mrow></mrow>
</mrow> That said, if we had a new MathML 4 <menclose intent="cancel($content)" notation="updiagonalstrike">
<mrow arg="content">...</mrow>
</menclose> |
Another accessibility example is drawing a box or circle around an
@dginev's idea of using |
First, menclose was removed from the first release of MathML Core because it had very bad state (I mean, to present it to people as a new feature with browser's high bar requirements), even with the clarification and simplification that were in MathML Core. So it was likely to add extra effort (spec, test, implementation, 'convincing non-mathml people'). If we want to integrate it for MathML Core, I think we need to do it very carefully. My suggestion would be:
|
This addresses some discussion from the 24/5/24 meeting that came up in relation to what should go in in the accessibility tree.
Although
menclose
can be done via CSS, the CSS can be quite complicated, especially for arrowheads (see the polyfill for some css). Standardizing this via the notation attribute would simplify the MathML need. It would also enhance accessibility because strikeouts/cancellations and other modifications would be visible to AT.Note: there is a PR about this. It references the closed issue #105.
The text was updated successfully, but these errors were encountered: