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

MathML-Core Agenda, Monday Feb 24, 2025 #284

Closed
bkardell opened this issue Feb 21, 2025 · 3 comments
Closed

MathML-Core Agenda, Monday Feb 24, 2025 #284

bkardell opened this issue Feb 21, 2025 · 3 comments

Comments

@bkardell
Copy link
Collaborator

bkardell commented Feb 21, 2025

- Make ::first-letter and ::first-line pseudo-elements not applied to elements with display: math #211
@brucemiller
Copy link

Are there any new thoughts on when stretchiness should apply? #270

@dginev
Copy link

dginev commented Feb 24, 2025

It would be nice to have a 1 minute retrospective on the results of WPT Interop 2025. MathML had two interop issues, 787 and 861, neither of which attracted support.

@bkardell
Copy link
Collaborator Author

Minutes:

02/24/2025 MathML Core Meeting

Attendees

  • Brian Kardell
  • Neil Soiffer
  • Louis Maher
  • Deyan Ginev
  • Bruce Miller
  • Murray Sargent
  • David Carlisle
  • Paul Libbrecht

Regrets

Action Items

2. Issues for publishing CR draft #170

No updates.

3. Update Implementation report link / verify tests #283

ACTION BK: Replace what we have in issue 283 with a link to a list of test which we can maintain.

4. Clarify the language around deprecated features of MathML #279

action NS will open an issue on whether the items that NS lists can be called presentational hints. Presentational hints allows you to style multiple HTML elements consistently using a single CSS file.

action BK will talk to MDN about how to name things in full but not in core.

ACTION** DC: To make a PR to core spec to list some items from issue 279 that are not to be added to core and considered deprecated by MDN. Wording to be reviewed later.

5. U+002D HYPHEN-MINUS in operators #70

6. Rename OverShift and UnderShift for munder/mover/munderover layout #121

action BK will send MuS information on writing web platform tests.

1. Announcements/Updates/Progress reports

Agenda Items

1. Announcements/Updates

DG wrote:
MathML had two interop issues, 787 and 861, neither of which attracted support.

BK: Put together a list of MathML projects that Igalia would support. They had hoped to inspire other funders. This did not work for Interop in 2025. BK is reaching out to other possible funders.

BK: We should keep proposing MathML projects in future years. We can propose the same projects that we proposed in 2025.

2. Issues for publishing CR draft #170

No updates.

3. Update Implementation report link / verify tests #283

BK wrote:
Currently we have an implementation report list which uses a query on wpt.fyi. At some point it started generating some false positives thanks to some JavaScript's APIS, and now it is getting others thanks to CSS ones. The web-dx group has been going through and mapping features.. It is a lot like what we do for interop scoring in general. I'm not 100% sure how to query it yet, but I'm working on it -- meanwhile we should work to verify/improve https://github.com/web-platform-dx/web-features/blob/main/features/mathml.yml and then update the spec link accordingly.

BK: We need to have a link to an actual list of tests. The tests are in the YAML file.

BK: Make sure that this YAML file is updated, and we have an actual list of tests that cover MathML.

DG: There are 115 entries in the list now.

NS: We need to have something that points to the actual pass/fail for the tests.

BK: There are a lot of false positives.

BK: Must look at how to create the link. We need to mark which tests are MathML.

ACTION BK: Replace what we have in issue 283 with a link to a list of test which we can maintain.

4. Clarify the language around deprecated features of MathML #279

In issue 279 NS wrote:
NSoiffer's general comment: the core spec mentions several features in MathML full that are "presentational hints". These include "mathcolor" and mspace's "width" attribute. These can be handled via UA style sheets. I think (as I indicate below), many of these incompatibilities can be resolved in this manner. In addition to reducing incompatibility, doing this means people do not have to invent their own methods for implementing these features. MDN currently lists "mathcolor" as deprecated which I do not feel is appropriate.

action NS will open an issue to see if people agree that the items that NS lists can be called presentational hints. Presentational hints allows you to style multiple HTML elements consistently using a single CSS file.

NS: There is this tension between deprecated and experimental If something is in full but not in core.

BK: If you think it could ever get in core, then list it as experimental.

NS: The original idea with core was We need to find some minimal amount of things that people will implement.

DG: Voted for deprecation because he does not think they will ever be implemented.

DG: Many of these items seem to be level 2.

BK: There was a request that the spec be clearer about the status of items. If we have two or three categories, we should list them in the spec.

DC: The full spec may describe an attribute and simply say they are not in core.

BM: We should talk to MDN to get a new term for things that are not in core but maybe someday.

BK: MDN wants to focus on things that will be in the browser.

NS: You cannot deprecate something that has never been in core.

BM: MDN should say "available in full only", instead of saying deprecated.

action BK will talk to MDN about how to name things in full but not in core.

ACTION DC: To make a PR to core spec to list some items from issue 279 that are not to be added to core and considered deprecated by MDN. Wording to be reviewed later.

5. U+002D HYPHEN-MINUS in operators #70

MuS: U+2212 is not a hack to write the minus sign, it is the definition of the minus sign. most software changes U+002d to U+2212.

Copilot says:
U+002D represents the Hyphen-Minus (-). It is commonly used as a hyphen, minus sign, or dash in text.

DC: The question is what to do with the U+002D case. You should use U+2212.

MuS: You used to search for a - b and find it but everything is a special symbol now.

NS: There is a huge legacy issue. Probably half of all mathematical documents have U+002d for minus instead of U+2212. For this reason, U+002d must be accepted as a minus sign.

BK: Someone could write a platform test for this.

In issue 70, NS wrote:
The WG discussed this again today. We reiterated the need for core to support this based on the vast amount of MathML out there that uses U+002D. We also
verified that both Safari and Firefox still map U+002D to U+2212, so Chrome is out of step with those browsers.

It is still the case that both a spec update and (we think) a test need doing.

6. Rename OverShift and UnderShift for munder/mover/munderover layout #121

DC sent this link to the group:
math/documentation/building-math-fonts/index

BK: We are waiting for confirmation from Microsoft.

MuS: The thing that bothers me more is the superscript and subscript shifts Which should be uniform for uniform Letters like A and B.
It really looks odd. Tech would never think of shifting them differently, and the OpenType spec says to shift them the same.

MuS: It is pretty elementary. I mean, that really shows up all over the place if you have a squared plus b squared equals c squared. Immediately you see, whoops, the two on the B is still a little too high, and, you know, it shows up in Safari. It shows up in Firefox, it shows up in Chromium. It does not show up in MathJax. It does not show up in Word. It does not show up in Tex or LaTeX.

MuS: So, I think that should be fixed. I mean, basically, whatever their shift is for A, just use that for B. It is going to look better.

NS: Let us look at the spec and see if there is wrong wording.

DC: It is saying that the subscript position for single characters depends on the font parameter not the height of the character.

NS: Perhaps it is an implementation bug.

NS: There's probably just a bug in the code, but it's curious that it shows up in Safari, Firefox, and Chromium. So, unless there is some override that I am missing, It is maybe an implementation bug and there should be a web platform test with a square. I mean, yes, E squared and B squared, and the two should always be the same.

NS: Perhaps MuS could write a test.

action BK will send MuS information on writing web platform tests.

MuS: As far as OverShift and UnderShift are concerned, I had not looked at that one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants