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
* Prevent MathJax nodes from being identified as 'unlikely candidates', and prevent <mjx-math> tags from being removed due to attribute aria-hidden="true"
* Revert changes to _isProbablyVisible() and isNodeVisible()
* Update test case to include the MathJax tags which are produced once client-side rendering is complete. The previous test case only used the static HTML received from the server.
Unfortunately, after htmltidy2 processes the page it is determined to be "unreaderable" though the appropriate JSDOM tests run and pass. Alternatively, if htmltidy2 is skipped, JSDOMParser produces a slew of errors.
Perhaps this will do for now...
* Adding support for file:// URLs. This is useful when the test case contains dynamic content as it allows the dev to save a copy of the rendered DOM to disk and use the resulting file as input to generate-testcase. Alternatively one could use JSDOM's {runScripts: "dangerously", resources: "usable"} options, but in my case these fell short and caused MathJax to crash due to missing localStorage implementation in JSDOM. Perhaps my approach will be useful to others...
* Use url fileURLToPath to handle file urls
---------
Co-authored-by: Gijs Kruitbosch <[email protected]>
Replacing `slug` with the identifier the test should use, and providing a URL
48
-
to an actual article on which the test should be based.
48
+
to an actual article on which the test should be based. If your test case involves dynamic content, you can save the page to disk and pass the file as a `file://` URL.
49
49
50
50
On macOS, you may need to make the `tidy` binary executable before that script will succeed. If you see an `EACCES` error when running that script, try:
0 commit comments