-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chrome_print()
hangs when printing html with maths produced by Quarto
#320
Comments
About this, did you try to increase the timeout already ? |
Yes, I tried increasing the timeout to no avail. Also, if you remove the inline maths (by deleting the |
Thanks for the report. I'll try to have a look into this. It seems related to how mathjax is loaded then... something seems to hang the page load and the expected websocket message is not sent. This is not easy to debug. In the meantime you could try another chrome R package (like chromote or crrri) that could communicate with chrome, but I suspected it will be the same error. Changing the HTML math method for the format may be the best workaround for now. |
I'd suggest that you try |
I can confirm that using I can consider this issue closed, however I guess the bug with |
We'll keep that open to see how we could fix the issue with this Mathjax loading. I don't think this is a timing issue but rather something related to how it is loading, and the websocket process not intercepting and so hanging. |
Hi,
I've been having issues using
chrome_print()
to produce a pdf from html that I have made from a Quarto document. Digging deeper I have found that it's due to the presence of maths symbols. I am not sure where in the document pipeline the failure is occurring, as the same document renders when using RMarkdown instead of Quarto.Here's a minimal example of what I'm doing:
Quarto doc:
Rendering this to produce 'test.html' I am then experiencing the failure (where
chrome_print()
hangs indefinitely) when running:I get the following errors:
Any advice or ideas of things I could check would be appreciated!
Session info:
The text was updated successfully, but these errors were encountered: