-
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
mstyle mathvariant inheritance and mi #53
Comments
I think we decided to ignore this case because people should really (1) use mathvariant on on token elements only (2) use transformed unicode character directly instead of mathvariant="bold-italic". I think we would need to think about the impact and details of this. For example, that it should probably be
since mathvariant is not restricted to mstyle in MathML Core. Or maybe the computed value of of text-transform: math-auto should depend on the inherited value instead. |
Since the case that @faceless2 mentions is legal although maybe not a good idea in practice, it needs to be tested (doesn't seem to be at this point in time). At the meeting today, @bkardell was doubtful that the
suggested fix above is appropriate. |
The suggested behaviour of
So provided Specifically, and assuming the proposed math text-transform values in w3c/csswg-drafts#5386 were approved: if the I'm aware the propose additional math text-transform values are not yet approved, but this might make the case for them a bit stronger. |
I don't remember if there was any progress on this. @faceless2 do you know the status? |
@faceless2: if you agree, can you close this issue? |
We've run into this in an example we're testing with:
The user-agent rule
mi { text-transform: math-auto }
is overriding the ruletext-transform: math-bold-italic
which it's inheriting from the mstyle.I'm aware that there will be some changes from MathML3, and from reading w3c/mathml#1 and https://lists.w3.org/Archives/Public/public-mathml4/2019Mar/0007.html it seems you're aware of this situation already. But I couldn't find a resolution for this specific situation.
If overriding the
mathvariant
attribute on the mstyle is intentional, that's fine. But if not, it's quite easy to continue to support this syntax by addingto the user-agent stylesheet.
The text was updated successfully, but these errors were encountered: