Kevin Barabash

Maybe we could provide that as an option and then people could choose between using SVG or setting `minRuleThickness`.

I filed a Chromium issue: https://bugs.chromium.org/p/chromium/issues/detail?id=1131046.

@ibrahima I wasn't able to repro the issue with `\overline{123}` in Version 87.0.4280.88 (Official Build) (x86_64).

I tried to reproduce the issue using BrowserStack, but the free account I have only provides access to Chrome 86. 😞

We already have some conditionals thanks to @edemaine in #975. In particular `\@firstoftwo`, `\@ifstar`, and `\@ifnextchar` were added. Maybe we should also add `\@secondoftwo` as well.

The goal here is to provide a solid base of macro support so that people can extend KaTeX functionality by using existing macros with minor or no modification from existing...

All functions as macros sounds like a big change, but it would make things more regular. Are there any other macro abilities a change like this would enable beyond allowing...

Cool. We should probably make this change at some point. I think we should finishing add flow types to Parser.js and extracting functions into the `functions/` folder before starting this....

I definitely think that `Parser` should be telling `MacroExpander` what mode we're in.

@3r3n-n go for it. Maybe try converting a couple uses of `.not.toParse()` and put up a PR to see what other people think about the change before converting the rest.