Kevin Barabash

I'm using v0.24. Here's the .fsproj file for the project in question: ```xml net8.0 Escalier.Playground ```

`$\c{o}\b{o}\={o}\showlists$` yields: ``` .D\mathord .D.\hbox(5.67776+1.93747)x15.00005 .D..\kern 0.27779 (for accent) .D..\OT1/cmr/m/n/10 ^^X .D..\kern -4.72223 (for accent) .D..\OT1/cmr/m/n/10 o .D..\vbox(4.30554+1.93747)x5.00002 .D...\hbox(4.30554+0.0)x5.00002 .D....\glue(\tabskip) 0.0 .D....\hbox(4.30554+0.0)x5.00002 .D.....\OT1/cmr/m/n/10 o .D....\glue(\tabskip) 0.0 .D...\glue(\lineskip) 1.07639 .D...\hbox(0.86108+0.0)x5.00002 .D....\glue(\tabskip)...

The ogonek looks tricky because it's position changes depending on the character. Look at the differences between the lowercase 'e' and 'a' on https://en.wikipedia.org/wiki/Ogonek.

@azotova It uses {array}, but {cases} is a separate environment. Could you open a new issue for it?

Request for {cases} environment in https://github.com/Khan/KaTeX/issues/278.

Prefixing class names shouldn't be difficult. It definitely reduces the likelihood of collision. I don't recall any issues reported that stemmed from CSS classname collision though.

I just read #1445. I guess it's an issue.

@edemaine thanks for adding this to the milestone.

Prefixing with `katex-` or `kt-` seems like the right way to go. I have a slight preference for `katex-`, but it's longer. This could be mitigated by using the full...

There's a tool for generating Flow types for CSS Modules: https://github.com/skovhus/css-modules-flow-types and TypeScript plugin: https://github.com/mrmckeb/typescript-plugin-css-modules.