Why is this breaking in instant mode?

[facelessuser]

So recently, I've finally been experimenting with instant mode again, and it works great. It allowed me to create interactive playgrounds for Python over here. Pyodide loads once for the site, and resposne is pretty good.

So I've been trying to get instant going in Pymdown Extensions. But there seems to be some weird issue related to instant. I had to switch over to KaTeX as MathJax is just too hard to get going in instant, but let's take both of them out of the equation. So in this example, I'm not running any math JS libraries. simply running Arithmatex in generic mode:

  - pymdownx.arithmatex:
      generic: true

So it is just spitting out <div> elements with escaped text. But only when instant is loaded, I get all sorts of errors in the console:

What is it doing and how can I make it stop? 🙃

[squidfunk]

Hmm, I need a reproducible example to debug this. I've just checked and instant loading works nicely with Arithmatex. I've also tested with the \begin{align} syntax, replacing the $$ I'm using in the docs in the MathJax guide:

\begin{align}
\operatorname{ker} f=\{g\in G:f(g)=e_{H}\}{\mbox{.}}
\end{align}

Everything renders as expected.

Edit:

I'm not running any math JS libraries

If I remove the Math libraries, the content is just rendered as-is. No errors in the console.

[facelessuser]

Okay, I may look into this sometime soon 🙂.

[facelessuser]

There seems to be other issues with instant parsing stuff it seems. I think it was parsing some UML SVG stuff.

Error: <tspan> attribute dy: Expected length, "NaN"

Just creates a lot of noise.

[squidfunk]

As ever, a reproducible case and I can look into it. Possibly related to the DOMParser which is used to extract the content from the fetched HTML.

[facelessuser]

I understand, it was more of an aside, I haven't gathered all the details, it was mainly why I opened a discussion. I was more digging for an understanding of what Material was doing so I could better debug.

My plan is to dig deeper. It seems the parser is making some assumptions. I will open an issue once I understand things better.

[facelessuser]

The last one wasn't Material's fault, it's actually down in Mermaid. Some buggy code. Thanks again for the help!