Minutes: MathML Core meeting Oct 7, 2019

Note: we will meet again next week. Several members will be at Igalia at a
hackfest. If we can't find a quiet area, we may have to cancel at the
very last minute.


Attendees:

   -

   Fred Wang
   -

   Brian Kardell
   -

   Neil Soiffer


Regrets: Murray Sargent, David Carisle, Patrick Ion
Agenda:

https://github.com/mathml-refresh/mathml/issues/8#issuecomment-538263480

MathML Conference(s)/Event(s)?

    FW: There is a hackfest at Igalia next week. Not focused specifically
on MathML, but some MathML work will likely get done.

    FW: Igalia has some interest in hosting a small MathML meeting (e.g. at
the Igalia office?).

    FW: Maybe a meeting at TPAC sometime?

    NS: Probably should bring this up to the full group.

Operator Dictionary updates? (David)

   - U+1EEF0 and U+1EEF1 #6
   <https://github.com/mathml-refresh/mathml/issues/6> => proposal: use
   lspace=1,rspace=2 (like sum/product) and resolve this issue.
   - review of accent operators #151
   <https://github.com/mathml-refresh/mathml/issues/151>
   - remove default stretchy property for multi-char operator #143
   <https://github.com/mathml-refresh/mathml/issues/143>

NS: It seems that we're kind of guessing at what the values should be.

FW: My proposal was because the default line spacing is thick-math-spacing,
maybe trying to do the same as other operators is better

NS: I can't offer anything better

FW: The proposal was to close the issue for now, do that and see if someone
raises an issue.  I think mostly we are waiting for David to update the
operator dictionary so we could do that.  I think we can move on since he
is not here or it isn't ready.

NS: I did note one missing operator that should be listed as having the
accent property.

NS: I see I think 3 that were missing, can we bring those over into #151
and build up a list of the ones we think we should remove accents from.
Does that sound reasonable to you?
FW: Sure

NS: 143 - default stretchy

FW: Here too we have work to be done. I prefer to get this all done and
update the spec, test, browsers.

NS: In the spec, are you bringing in the operator dictionary from somewhere
else?

FW: It is generated from the file that David is maintaining, that's why we
want to get it right

NS: OK, that's where we need to make all of these changes.


DOM/IDL updates? #83 <https://github.com/mathml-refresh/mathml/issues/83>
#138 <https://github.com/mathml-refresh/mathml/issues/138> #139
<https://github.com/mathml-refresh/mathml/issues/139> #140
<https://github.com/mathml-refresh/mathml/issues/140> (Brian)

    BK: FW is working on them

    FW: There are some tests that have been added. Been added to Webkit,
Gecko, and Blink. Added some WPT tests in addition to what BK has done.

    FW: tried to write a patch for Firefox and added more tests. Patch has
landed along with the test changes

    FW: Now Gecko is at same level as Webkit.

    BK: Are these based on their nightlies so eventually will be in default?

    FW: Yes, so in Gecko and Webkit. Also in Igalia branch of Blink.

Clarification for Operator maxsize/minsize: #109
<https://github.com/mathml-refresh/mathml/issues/109> #110
<https://github.com/mathml-refresh/mathml/issues/110>

    FW: There is some text already in the spec that is what firefox and
safari do and what we intended to do in Chromium - just wanted to make sure
it makes sense first.  For example, what happens when min-size is greater
than max-size. Mathplayer does something different (the opposite)?

    NS: Yes, I think so.  We have to resolve it somehow.  If we have some
conflict we treat it as the

    FW: when maxisze<minsize, treat maxsize=minsize

    BK: is there a precedent in CSS with minwidth and maxwidth?

    BK: See https://drafts.csswg.org/css-sizing-3/#width-height-keywords.
Will add what I find to #110 -- it isn’t obvious what is done when reading
the spec.

   -

   If the min-width is specified with a value greater than max-mix, the min
   width will be the one that is applied

Remove explicit mo@maxsize = "infinity" #107
<https://github.com/mathml-refresh/mathml/issues/107>

    NS: Can this be set on mstyle, because if it can, then we need a way to
override it.

    FW: No, can’t be set there. So don’t need to override. Only in operator
dictionary (where it is not explicitly mentioned)

    NS: Then I agree it is not useful

    FW: mstyle still allows it in full

    NS: so we need a polyfill

    RESOLVED: remove the maxsize value ‘infinity’ in core

WHATWG HTML5 #145 <https://github.com/mathml-refresh/mathml/issues/145>

   -

   would referring to MathML Core (draft) instead of MathML3 (W3C rec)
   cause any problems?

    Broad discussion on whether it is good (by several measures) for whatwg
to link to core (or when). No resolution.