Jakub T. Jankiewicz

I have no idea what you found because I'm not able to reproduce. Can you maybe record a video where you have the issue? I've added a viewport meta tag...

@jacknely I'm not able to reproduce. Can you record a video? Also what kind of system you're using?

Also what kind of keyboard, if the system allows to change it (like on Android).

@jacknely thanks, I'm able to reproduce on browser stack, on my phone I use different keyboard when to type `-` I hold the key. Something needs to be off on...

@porksausagex180 did you use, the symbol keyboard?

This is not memory leaks, basically, almost any library or project, if you keep Adding DOM nodes it will make the memory grow. THis is how websites work. Just try...

there is one thing that may cause memory growth, which is cache. To speed up rendering there is a cache that saves all output in `Map` I can maybe create...

There is `clear_cache` method, I think that It's not documented.

I've added milestone 2.33.0, I don't use them much, but this will make me prioritize the issue. Since I think it's critical. Memory leaks are bad.

There are two issues: * cmd had cache for formatting to prevent multiple processing of text when the user moves the cursor over text, I'm not sure if that one...