-
Notifications
You must be signed in to change notification settings - Fork 9
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
Browser Policy #13
Comments
That's interesting. Can you please verify if I am loading it from the following source: MeteorMathJax.sourceUrl = 'https://cdn.mathjax.org/mathjax/latest/MathJax.js?config=TeX-AMS-MML_HTMLorMML'; which can be changed BTW, by overwriting the |
Leaving a comment on an old issue because this came up in a Google search for the CSP violation. See https://github.com/mathjax/MathJax-docs/wiki/JavaScript-MathJax_Blank-font-error and mathjax/MathJax#256: MathJax purposefully loads a non-existent font to test browser behaviour. It’s possible to add |
@cmbuckley I am happy to accept a PR if you have an idea how to approach this. |
Unfortunately, I don’t think there’s an easy solution. MathJax does this behaviour by design, so users either need to accept the behaviour, or accept the CSP violation! |
Then perhaps, this is a good issue to report at |
You’ll notice I linked a MathJax issue from 2012 in my first comment. As I say, this is by design, so I don’t think there’s anything that can be done! |
@cmbuckley Ah, you're completely right. Sorry about missing that detail. I am quite distracted today. |
Hey! Quick question and I hope I am not missing something basic, but when implementing MathJax, I am also using browser-policy, and am receiving issues with loading the font. Specifically the error is:
Refused to load the font 'about:blank' because it violates the following Content Security Policy directive: "font-src 'self
Is there a specific browser policy that is necessary when loading in MathJax that you would be aware of? I have allowed loading from mathjax.org. Any assistance would be greatly appreciated.
The text was updated successfully, but these errors were encountered: