Skip to content
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

Custom MathML elements #138

Open
fred-wang opened this issue Sep 16, 2019 · 3 comments
Open

Custom MathML elements #138

fred-wang opened this issue Sep 16, 2019 · 3 comments
Labels
css / html5 Issues related to CSS or HTML5 interoperability level-2 need tests Issues related to writing WPT tests

Comments

@fred-wang
Copy link

cc @bkardell

Just opening this for the record...

It seems Gecko supports custom elements in the XUL namespace and there is a web components discussion to allow it in any namespace (e.g. SVG too) WICG/webcomponents#634

IIUC the proposal is also to remove the dash requirement for non-HTML namespace, although I'm not exactly sure how that would work with the HTML5 parser.

We already discussed this informally in the MathML CG and agree it would be important to implement MathML elements that are not in the core spec.

@fred-wang fred-wang added MathML Core Issues affecting the MathML Core specification css / html5 Issues related to CSS or HTML5 interoperability need tests Issues related to writing WPT tests need resolution Issues needing resolution at MathML Refresh CG meeting need specification update Issues requiring specification changes labels Sep 16, 2019
@bkardell
Copy link
Collaborator

I believe this should move to v2, we aren't going to get there in one step but opening the important discussions of how to align to move forward is the point. Realistically if we have unknown elements we can do most of this part and alignments are mostly important for other steps.

@fred-wang
Copy link
Author

from june 1: level 2

@NSoiffer
Copy link
Contributor

NSoiffer commented Aug 3, 2020

Resolved (again?) that this should go to level 2.

Note that the core spec currently labels these as "Unknown MathML element" and provides a few rules about layout if their display value is math or inline-math. I believe no spec change is needed and that this is compatible except if we all extensions of MathML elements such as mfrac, in which case level 2 will need to make changes to that wording (in addition to specifying how these work).

@NSoiffer NSoiffer removed MathML Core Issues affecting the MathML Core specification need resolution Issues needing resolution at MathML Refresh CG meeting need specification update Issues requiring specification changes labels Aug 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
css / html5 Issues related to CSS or HTML5 interoperability level-2 need tests Issues related to writing WPT tests
Projects
None yet
Development

No branches or pull requests

3 participants