MathML-Core Agenda: Jan 29, 2024

[bkardell]

Start with a few updates: republished, chrome issue fixed, some funding, HTML points to MathML-Core...

Then I would really like to try to focus on some house cleaning. We currently have 78 open issues. 20 of those are for level 2, but that still means we've got 58 issues open and only 62 ever closed, a not small number of those are the the monthy agenda issues since we started doing that.

Particularly I think it is worth a quick scan/discussion of these, and perhaps whether we might want to schedule a special session to work through some of it...:

• 11 open items claim to need of spec updates. Do they?

• 11 open items claim to need tests. Do they?

It might also be useful to "start at the back" and look at these few which have been open since early 2019:

• Add rules to map from non-combining to combining accents
  

• TeX-like spacing rules
  

• Negative spacing

• Define what baseline things align against

• Define what inline percentages resolve against

• Define what block percentages resolve against

• Interpretation of DisplayOperatorMinHeight

• Add text to describe what should happen when not using an OpenType font

• Define fallback for OpenType MATH parameters

[bkardell]

Minutes:

01/29/2024 MathML Core Meeting

Attendees

• Brian Kardell
• Neil Soiffer
• Louis Maher
• David Carlisle
• Deyan Ginev
• David Farmer

Regrets

Agenda Items

Announcements/Updates

republished

BK: We want to submit for wide review, and we want to get the html spec updated.

BK: The HTML PR is updated so it points to core now. We got republished.

BK: We have instructions from BB on how to ask for a wide review for CR.

We need a privacy and security section which we have, but have not submitted yet.

chrome issue fixed

BK: Chrome bugs have been fixed on hex transforms.

BK: There were multiple bugs, but they were like the same thematic bug. They concerned text transforms and math.

some funding

NS and MuS donated additional funding to the core collective.

Issues

I would really like to try to focus on some house cleaning. We currently have 78 open issues. 20 of those are for level 2, but that still means we have 58 issues open and only 62 ever closed, a not small number of those are the monthly agenda issues since we started doing that.

Particularly it is worth a quick scan/discussion of these, and perhaps whether we might want to schedule a special session to work through some of it...:

font enumeration in -core privacy-needs-resolution

Resolved to close this issue as there is nothing special to do here, it is just CSS and we have logged the relevant parts in the spec already.

11 open items claim to need of spec updates

Do they?

issue 57
Describe how to layout DOM elements violating HTML5 model

BK: Nothing to test here.

From Brian Kardell to Everyone: https://wpt.fyi/results/html?label=master&label=experimental&aligned&q=mathml

BK: There are 21356 tests which it passes.

DC: text nodes need specification similar to unknown elements.
The case of a text node is not handled in the spec.

BK: Can not close this one. It needs tests.

issue 70
U+002D HYPHEN-MINUS in operators

NS: Many people think this is important. It is not mentioned in the spec.

NS: I think we need to mention it. We need to add a test.

NS: If Chrome does not implement the change, then the test will break in Chrome. Firefox and Safari support it.

DG: Recently I have hit on 2 new dash uses in MathML context.

DG: One is the range 3 dash 8 is 3 to 8. How is there going to be a way where we can still use a dash that does not get mapped to hyphen, for the uses that are not minus.

NS: I would say Mtext would be your way to do that so it is an MO would be unified with the Unicode minus, but an Mtext would not.

NS: On the other hand, I have to say that usually when you do have a range you tend to want to have a longer dash.

NS: I had not thought about wanting to have a dash.
DG: So use a dash specialized for the occasion of the right length and that will be left alone without mapping.

ACTION NS will add a spec change and a test and add them via pull requests.

issue 121
Rename OverShift and UnderShift for munder/mover/munderover layout

DC was waiting for feedback from Microsoft.

ACTION DC will edit the spec once he receives input from Fred and MuS.

BK: suggested that individuals could look through this list; and, if they were familiar with the subject, that they could make decisions about these issues.

issue 138
Standardize layout constraints for operator stretching

DG: it looks like this could be nominated for level 2.

BK: This should be level 2. It is a new question for CSS. Give it a level 2 label.

BK: Individuals can look at this issue and see if they want to work it.

issue 129
Properly define DOM/IDL relationships

DC writes: Interoperable version (MathMLElement) is deployed in all major browsers. The name of the interface is not important.
Other issues may be opened in a new issue for level 2.

BK: Close this issue.

issue 77
Define what block percentages resolve against

BK: Here is a test case:
From Brian Kardell to Everyone: https://www.software.hixie.ch/utilities/js/live-dom-viewer/?saved=6693

BK: It is not interoperable.

DC writes: Still needs spec change (spec still has issue link note)

DG: The needs test label should be satisfied.

NS: Not handled in the spec.

NS: It still needs a spec change.

issue 132
Negative spacing

The current labels for issue 132 are:

MathML Core
need specification update.
need tests.

BK will ping Fred and see why he removed {"needs resolution".

DC to Fred Wang: could you clarify what specification change you had in mind when adding the label?

NS It maybe that negative L and R space are not a problem any longer.
This is what the spec says.

You can now have negative values.

DC will ping Fred and ask him what he wants.

BK asked the people to go through the two filtered lists and see what should be closed.

The 1/29/2024 MathWG Core meeting ended here.

11 open items claim to need tests. Do they?