Skip to content

Matching: use queuMathJax instead of typesetPromise#1172

Merged
bnmnetp merged 1 commit intoRunestoneInteractive:mainfrom
ascholerChemeketa:matching-mathjax-fix
Mar 8, 2026
Merged

Matching: use queuMathJax instead of typesetPromise#1172
bnmnetp merged 1 commit intoRunestoneInteractive:mainfrom
ascholerChemeketa:matching-mathjax-fix

Conversation

@ascholerChemeketa
Copy link
Contributor

I believe this should fix:
https://groups.google.com/g/pretext-dev/c/iIy3kSG-WqY/m/9IsTgEPjAgAJ?utm_medium=email&utm_source=footer

And possibly:
#762

I don't believe matching should be triggering a full typesetPromise on init. Depending on the timing, this can cause the typeset that is supposed to process the rest of the page to try to convert elements that have already been converted.

Definitely should only target its own content. Not sure about using queueMathJax, but that seems wise too.

@bnmnetp bnmnetp merged commit 9c8de81 into RunestoneInteractive:main Mar 8, 2026
@bnmnetp
Copy link
Member

bnmnetp commented Mar 8, 2026

Thanks, the components should always use queueMathJax to ensure we are not trying to typeset multiple things at the same time. This one just didn't get updated from the initial prototype.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants