Minutes_ MathML Core meeting 28 October_ 2024

10/28/2024 MathML Core Meeting<https://github.com/w3c/mathml-core/issues/264>

Attendees

  *   Brian Kardell
  *   Louis Maher
  *   Paul Libbrecht
  *   David Carlisle
  *   Deyan Ginev
  *   Bruce Miller
  *   Neil Soiffer
Regrets

Action Items

NS will submit more tests to the interop intent effort. DG may also submit more tests.

Open \Big/ and \Big\backslash etc are too small #261<https://github.com/w3c/mathml-core/issues/261>
DC Characters stretch if the font lets them stretch. Issue 261 is closed as completed.

Too much space around / #260<https://github.com/w3c/mathml-core/issues/260>
DC: Let us wait to see if there is a possibility to change the spacing around / in browsers.

Interaction between height and baseline alignment #259<https://github.com/w3c/mathml-core/issues/259>
DC left this comment in issue 259: Fred Wrote: But maybe what is more natural is to tweak the line-ascent/line-descent evenly so that the baseline is unchanged.
DC wrote: The WG discussed this on the call 2024-10-28 and we think this baseline alignment does sound more natural.

Missing autofocus attribute for MathML elements #258<https://github.com/w3c/mathml-core/issues/258>
DC Closed issue 258 after today's core meeting because the actions were already done.

Consider support for the box-sizing property #257<https://github.com/w3c/mathml-core/issues/257>
RESOLVE On issue 257 add support for the box-sizing property. We will leave issue 257 open until we know if we need spec updates or the work is completed.

ACTION PL asked BK to put MathML support in the HTML Sanitizer issue 227<https://github.com/w3c/mathml-core/issues/227> on the agenda for the following core meeting.

Agenda Items

Announcements/Updates
NS will submit more tests to the interop intent effort. DG may also submit more tests.

Open \Big/ and \Big\backslash etc are too small #261<https://github.com/w3c/mathml-core/issues/261>
NS: Utr25 should say which character stretch and which do not.
DC Characters stretch if the font lets them stretch. Issue 261 is closed as completed.

Too much space around / #260<https://github.com/w3c/mathml-core/issues/260>
DC: It got normalized at some point, since MathML 3, to have the same space as other binary operators like plus.
DC: Is it feasible to change the spacing around / in chrome and other browsers? If not then we accept what is called for in the core spec.
MoS writes: I was hoping that changes to Unicode.xml would trickle-down to the browser implementations. Otherwise, it seems like a chicken and egg problem. It is not that this is a request to implement a new feature, but only to change a value in a table. As per discussions above, the rationality seems sensible, and if not us mathematicians, who could judge what the "right" spacing is? If there is any argument why a larger spacing might be better, we could discuss that, but to keep it as it is since browser vendors might not like it does not seem like an ideal solution to me.
NS: All that is required is to move / from one category to another. It should be a simple change.
DC: It was probably a mistake originally.
NS: Can we move it from category B to category K in appendix B of the core spec?
DG: Wouldn't that make it non-stretchy? So, you get the right spacing, but it will not stretch.
DC: / wants to be stretchy. It can be stretchy in some fonts.
NS: It does stretch, I think.
DG: It can stretch in Stix.
DC: It does stretch in some fonts, not all fonts can stretch diagonally.
Ns: The work around is to set lspace and rspace to zero.
DC: Let us wait to see if there is a possibility to change the spacing around / in browsers.
NS: Let us wait until we hear back from Fred.
NS: I think \ has zero spacing.
DC: \ spacing is zero, but \ is not stretchy.
DC \ has zero spacing because no one really looked at it as having any spacing. That is just its default.

Interaction between height and baseline alignment #259<https://github.com/w3c/mathml-core/issues/259>
DC left this comment in issue 259: "Fred Wrote: But maybe what is more natural is to tweak the line-ascent/line-descent evenly so that the baseline is unchanged.
DC wrote: The WG discussed this on the call 2024-10-28 and we think this baseline alignment does sound more natural."
DC: If Fred made Chrome, WebKit, and Firefox all do the same thing, then we should just specify that in the spec.

Missing autofocus attribute for MathML elements #258<https://github.com/w3c/mathml-core/issues/258>
DC Closed issue 258 after today's core meeting because the actions were already done.

Consider support for the box-sizing property #257<https://github.com/w3c/mathml-core/issues/257>
LM: From copilot "The box-sizing property in CSS controls how the total width and height of an element are calculated. It determines whether padding and borders are included in the element's total dimensions or not. There are two main values:

  *   content-box: The default value. Width and height apply to the element's content only. Padding and borders are added to the outside of this. border-box: Width and height include the content, padding, and border. This makes sizing elements more intuitive because you do not have to add up the padding and border width to get the total size. Most modern layouts prefer border-box for consistency.
From Brian Kardell to everyone: MathML H1 report (2024) Published on October 9, 2024, by Igalia<https://opencollective.com/mathml-core-support/updates/mathml-h1-report-2024>
In Issue 257, DC wrote: "WG discussed this on the call today and encouraged adding of support for this property. Leaving open until we decide need spec updates and./or implementation completed."
RESOLVE On issue 257 add support for the box-sizing property. We will leave issue 257 open until we know if we need spec updates or the work is completed.
DG: Would issue 257 be appropriate to discuss men close?
ACTION PL asked BK to put MathML support in the HTML Sanitizer issue 227<https://github.com/w3c/mathml-core/issues/227> on the agenda for the following core meeting.
PL: I think we have basically two directions: one of them is to try to be minimal and the other is to try to be as global as possible.