Do not force sizing groups to display inline-block

[edemaine]

Fix #1788 by removing display:inline-block rule from .sizing, as suggested by @ronkok. I don't see why a sizing change cares about the display mode, and it fixes the interaction between makeVList and sizing commands, and didn't affect any screenshots beyond three invisible changes specific to Chrome. It should also allow me to remove a .sizing { width:min-content } rule that I had to add in #1787.

Here's how the example from #1788 now renders (without #1787): all Bs properly descend.

A\raisebox{-1ex}{B}
\large A\raisebox{-1ex}{B}
\huge A\raisebox{-1ex}{B}
\large {A\raisebox{-1ex}{B}}
\huge {A\raisebox{-1ex}{B}}

Here are screenshot diffs. As there are no red or green pixels, the changes are invisible:

[codecov-io]

Codecov Report

Merging #2044 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #2044   +/-   ##
=======================================
  Coverage   93.34%   93.34%           
=======================================
  Files          79       79           
  Lines        4992     4992           
  Branches      876      876           
=======================================
  Hits         4660     4660           
  Misses        291      291           
  Partials       41       41

Flag	Coverage Δ
#screenshotter	89.07% <ø> (ø)	⬆️
#test	86.51% <ø> (ø)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 45539c2...c55a20c. Read the comment docs.

[ronkok]

This seems reasonable to me. I can't think of a reason why a font-size change would require inline-block. This line of code has been here since KaTeX v0.6.0. That predates the vertical alignment changes in PR #768. If I had to speculate why the inline-block is there, I might look at the old vertical alignment code.

In any case, the inline-block now is a positive harm to vertical alignment. It's good that we are getting rid of it.

[kevinbarabash]

It's interesting that only the Chrome screenshots were affected. Different browsers different rendering engines I guess. 🤷‍♂️