-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add menclose to MathML core #216
Comments
I don't think order matters for the current set of values. However if it does need to be specified because of some CSS properties, the order in which they are listed seems reasonable to me. |
This was discussed at the CG meeting today. From the notes:
The CG felt menclose was important and since the other browsers implement it but Igalia currently doesn't plan to do it, this should move to level 2. There should be a polyfill to handle this. |
Filling in some details on the earlier comment... I created a codepen sweep test of the attributes.
|
Opening a new issue to track needed work for menclose ( PR of the original text: w3c/mathml-core#24 ).
Known issues:
Simplify: Simplification of the menclose element #105
menclose does not specify in which order the notations are painted ( menclose does not specify in which order the notations are painted #113 )
need OpenType MATH values if a dedicated algorithm is provided ( OpenType MATH values for menclose notations #97 )
Instead of a dedicated algo, it would be better if menclose would just use the current mrow algo and rely on pure CSS for styling notations.
The text was updated successfully, but these errors were encountered: