Minutes: MathML Core Meeting of Dec 16, 2019

Attendees:

   -

   Fred Wang
   -

   Bruce Miller
   -

   David Carisle
   -

   Brian Kardell
   -

   Neil Soiffer
   -

   Sam Dooley
   -

   Patrick Ion
   -

   Rob Buis
   -

   Murray Sargent


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



The meeting was recorded:
https://benetech.zoom.us/recording/share/MRIKVoayRlgrc6-Kk8LmC-isupSD5TQVLUWMLTe8pV2wIumekTziMw

Operator Dictionary (David)

   - any updates on fixing up entries
   - Make things more consistent and general review & fixup #87
   <https://github.com/mathml-refresh/mathml/issues/87> #6
   <https://github.com/mathml-refresh/mathml/issues/6> #151
   <https://github.com/mathml-refresh/mathml/issues/151>
   -

   NS: I talked to someone who will report some problems he found
   -

   DC: I could sense there was a reason why I shouldn’t start working on it
   last week :-)



OpenType questions for Microsoft (Murray)

   - https://lists.w3.org/Archives/Public/public-mathml4/2019Nov/0013.html
   - ink ascent/descent #128
   <https://github.com/mathml-refresh/mathml/issues/128>
   -

   MS: I plugged in a square of x in a denominator. The extra ascender is
   above the radical line.
   -

   NS: I think the issue is when the layout is done, is it the top of the
   bar or the top of the extra ascent.
   -

   MS: It includes that extra space in Word.
   -

   FW: The spec currently says the ink boundary.
   -

   NS: But this has issues with other boxes like mpadded, etc. Simpler to
   use the box boundaries.
   -

   FW: Yes, but need to worry about ink boundaries of characters. Problems
   with “_” and a few others.
   -

   FW: Everyone except Gecko does the above.
   -

   Resolved: do it the way everyone but Gecko does it. Simplifies spec and
   implementation.



   - interpretation of DisplayOperatorMinHeight: #95
   <https://github.com/mathml-refresh/mathml/issues/95>
   -

   Pushed off for later. Probably will ignore it.



Define if width/height/inline-size/block-size are supported: #45
<https://github.com/mathml-refresh/mathml/issues/45>

RB: added a patch to Chromium that handles all the main containers. The
team leads pointed out that it may be easier if we support width/height on
all elements. Just landed a patch with this that has this for the
leaf/container elements. Need to decide if we should support width/height.

RB: Makes sense to do this for containers. Seems weird to allow this in
square roots, etc, to get scroll bars.

DC: Yes would be weird to for normal math. But for computer generated math,
that can be weird. Might have half a mb of proof, so it could be useful
there.

PI: It would be unusual to specify a width on them, so they wouldn’t happen
in normal math.

DC: For multi-step proofs, being able to scroll intermediate steps could be
good

NS: Is there a downside to allowing it? Can it accidentally add scroll bars?

FW & BK: shouldn’t happen

DC: If it is there by default/easier to do, I think it could be useful.

RB: The whole layout system expects the w/h to be there, so it should be
easier. At least Ian (Google team lead) thinks it should be easier. Seems
reasonable to support them.

PI: Inline-size and block-size were mentioned earlier in this issue. Are
they independent?

RB: There is min/max w/d that comes along with w/d.

BK: They are different.

PI: Inline-size sets the horizontal (in western writing) so sets the width,
the block sets height. But the writing-mode defines it really; see the
definition.

BK: Take a look at https://codepen.io/bkardell/pen/KKwMPyg

NS: I think all should break, but I would expect the 2nd and 3rd (ones on
math elements) to break in a smart place.

BK: Is it reasonable to set a width on all of them and use common CSS?

DC: Yes.

NS: Do we have consensus?

RB: We need tests for all of them. mspace is special.

NS: mpadded also.

FW: My initial idea is still on github
<https://github.com/mathml-refresh/mathml/issues/45#issuecomment-511718819>.

FW: they aren’t really different, they are added on after the layout.

Resolved: all elements should support it. Details need to be worked out.

RB: Let’s have Ian look at Fred’s description.

Case insensitivity #178
<https://github.com/mathml-refresh/mathml/issues/178>

FW: there is a difference between ASCII case insensitivity and Unicode case
insensitivity. We need to make the spec clear about what we mean.

Resolved: Just say it is ASCII case insensitivity.