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

scriptlevel and displaystyle #388

Open
davidcarlisle opened this issue Jun 19, 2022 · 1 comment
Open

scriptlevel and displaystyle #388

davidcarlisle opened this issue Jun 19, 2022 · 1 comment
Assignees
Labels
MathML 4 Issues affecting the MathML 4 specification need specification update Issues requiring specification changes

Comments

@davidcarlisle
Copy link
Collaborator

https://w3c.github.io/mathml/#presm_scriptlevel

says of scriptlevel and displaystyle attributes:

They also may be set explicitly via the displaystyle and scriptlevel attributes on the mstyle element or the displaystyle attribute of mtable. In all other cases, they are inherited from the node's parent.

similarly the schema "adds" these to <mstyle>

https://w3c.github.io/mathml/#parsing_mstyle.specificattributes

and mstyle attribute table lists them:

https://w3c.github.io/mathml/#presm_mstyle_attrs

However all these descriptions come from Mathml3.

Core makes them global

https://w3c.github.io/mathml-core/#global-attributes

so in Full they are common to all Presentation elements.

https://w3c.github.io/mathml/#presm_presatt

So should not be described as specific to mstyle.


This is assuming we are happy to relax the use of scriptlevel in this way. (I do not recall why it was restricted in earlier versions).

If instead we want to keep the restriction, then the most natural place to do that would be to change Core so these are not global attributes there, but keeping Core as it is, and changing Full to match looks OK to me.

@davidcarlisle davidcarlisle added the MathML 4 Issues affecting the MathML 4 specification label Jun 19, 2022
@NSoiffer
Copy link
Contributor

I think the reason to avoid them on all elements was because that we didn't need to think about how they interreacted with an element that changed the scriptlevel. Putting all that logic on/isolating it to mstyle seemed easiest for the spec and implementations.

It seems safe to change them to be global, but we need to say that the new value overrides the existing value on the current element, not on the any children that change it (they make use of the new value as part of their changes).

@davidcarlisle davidcarlisle added the need specification update Issues requiring specification changes label Nov 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MathML 4 Issues affecting the MathML 4 specification need specification update Issues requiring specification changes
Projects
None yet
Development

No branches or pull requests

2 participants