MathML-Core (Rescheduled) Feb 27, 2024 Agenda

[bkardell]

• Wide reviews / MathML-AAM

• percentage of minsize/maxsize #103

• Make ::first-letter and ::first-line pseudo-elements not applied to elements with display: math #211 - can this be closed?

• Searching or matching text #220

• Idea: Consider introducing CSS math-leading-space / math-trailing-space properties #218

• Interpretation of spaceAfterScript for mmultiscripts's prescripts #217

• Misaligned brackets #215

[dginev]

• percentage of minsize/maxsize #103
  • This is a rare issue where MathML Core and MathML Full contradict each other, with different browsers today implementing one of the two definitions. Is there a path to return to interop? Or should implementers avoid using the feature?

[bkardell]

Minutes:

Attendees

• Brian Kardell
• Neil Soiffer
• Louis Maher
• David Carlisle
• Deyan Ginev
• Bert Bos
• Bruce Miller

Regrets

Agenda Items

Announcements/Updates

Wide reviews / MathML-AAM

NS: says that BK has been making progress on the fast checklist for the CR.

NS: said that it is a lot of work to do the wide review.

BB said it was a lot of work, but it was well-documented on how you go through the process.

BK wondered if all the forms were necessary because they may not pertain to our project.

BK: would like another person to help him with the horizontal review.

NS will help with this.

Issues

percentage of minsize/maxsize #103

Resolution: DC: We can close issue 103.

NS: And add a bug report for chromium. David and I agree that the MathML (false back)????

NS: I mean that the core and the MathML 4 are in sync as to the interpretation of percentages.

NS: David and I think that they are in sync.

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

BK: All agreed on this. We said seems logical, except, I looked at the web platform tests and I thought number 2 does not really seem correct to me.
And we talked about it and we decided that yes, number 2 was wrong. So, I updated the web platform tests. And not just 2 I also change 3. Fred was very happy with 2. But he was not satisfied with 3.

BK: So, I would like it if somebody could look. They are linked to the web platform tests.

BK: So, this is the change that is in question, I guess. I do not know if anybody has time to look at this and see I did not understand why this particular suggestion would matter. But, if anybody has a second to look at that and let me know what they think, I can change it, and we can get these merged, and then we can close this issue finally. But if not, it is okay, next week Fred and I are going to start more regular meetings between us since he cannot make it to these meetings so that we can make sure that we get his feedback.

ACTION: BK will ask Fred if some other meeting time would allow him to meet with our core group.

DC said he would investigate this issue.

CONCLUSION: We're looking for a second pair of eyes and advice on a web platform test that is first line first letter pseudo elements number 3, and if we can get that one last thing resolved, then we can merge these web platform tests and close issue 211.

Jump to issue 215 (Misaligned brackets), the last item on today's agenda.

Searching or matching text [#220](https://github.com/w3c/mathml- n chrome get core/issues/220)

Idea: Consider introducing CSS math-leading-space / math-trailing-space properties #218

Interpretation of spaceAfterScript for mmultiscripts's prescripts #217

Misaligned brackets #215

DG believes this issue is related to issue 103 (percentage of minsize/maxsize).

ACTION: NS: So, what I think the suggestion here or the action item David is to have 2 web platform tests, one of which is using the minsize maxsize and the other one without it and using ems.

NS: I think the example you had with the M sub sup from the other one was a good one.