You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While the querystring is usually more targeted for server usage, there is some Javascript code (running in the browser) which is using these querystrings as information to trigger specific behavior.
One example (encountered on libretext) is MathJax (2 at least). MathJax is loaded with a code like <script type="text/javascript" src="path-to-MathJax/MathJax.js?config=xxxx"></script>. MathJax uses the config=xxxx to know which configuration file(s) to load.
This is currently broken in warc2zim because of the decision we took to escape all querystrings (see the long discussion on pros and cons on #206). Querystrings are not query string anymore, and the JS code fails to find it.
Not sure how to fix it given the cons we know about keeping querystrings as-is. At least this should be more clearly documented.
Maybe escaping and keeping the querystring could be the solution (e.g. using something like <script type="text/javascript" src="path-to-MathJax/MathJax.js%3Fconfig%3Dxxxx?config=xxxx"></script>, with the ZIM entry at path-to-MathJax/MathJax.js?config=xxxx.
The text was updated successfully, but these errors were encountered:
While the querystring is usually more targeted for server usage, there is some Javascript code (running in the browser) which is using these querystrings as information to trigger specific behavior.
One example (encountered on libretext) is MathJax (2 at least). MathJax is loaded with a code like
<script type="text/javascript" src="path-to-MathJax/MathJax.js?config=xxxx"></script>
. MathJax uses theconfig=xxxx
to know which configuration file(s) to load.This is currently broken in warc2zim because of the decision we took to escape all querystrings (see the long discussion on pros and cons on #206). Querystrings are not query string anymore, and the JS code fails to find it.
Not sure how to fix it given the cons we know about keeping querystrings as-is. At least this should be more clearly documented.
Maybe escaping and keeping the querystring could be the solution (e.g. using something like
<script type="text/javascript" src="path-to-MathJax/MathJax.js%3Fconfig%3Dxxxx?config=xxxx"></script>
, with the ZIM entry atpath-to-MathJax/MathJax.js?config=xxxx
.The text was updated successfully, but these errors were encountered: