-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
LaTeX/MathJax broken using Firefox v82.0 #5374
Comments
Thanks @MRScheid - confirmed with FF84 on my Mac, at for example https://plotly.github.io/LaTeX-basics/ It looks like the LaTeX renders, but has some sort of bounding box error. |
@alexcjohnson when can we expect this to be fixed? |
We'll try to fix it in the coming weeks but we'd sure appreciate some help! |
On Firefox 84.0.2, I noticed that the latest version of MathJax 2.x (2.7.9) behaves very differently from the one checked into our repo (2.3). Based on this, I'm not sure there will be one solution that will work for both MathJax versions. For example, using my tentative fix, I get this on 2.7.9: On the other hand, Chromium renders the correct result for both MathJax versions. Would a fix only targeting MathJax 2.7.9 be good enough @alexcjohnson ? |
We can certainly upgrade to 2.7.9 and drop 2.3, especially if we can get this into our v2 release. In fact in a perfect world we'd upgrade to MathJax v3 in plotly.js v2, but I assume that'll be more than a one-afternoon change, so not something we can do right now. |
Ok, so I'll try to come up with a patch to fix the issue in MathJax 2.7.x! |
Is there any known workaround, or is LaTeX in Plotly just plain broken for all recent Firefox versions? |
Jan 28> We'll try to fix it in the coming weeks Is there any progress in half a year? Did there some serious difficulties appear? |
We did spend some time on this in February but ran into problems around MathJax versions so we put this aside until 2.0 was released (done last month!) wherein we committed to supporting MathJax 2.7.5 moving forward, and we also upgraded our testing infrastructure. Unfortunately, no one on our staff is available to fix this issue for the next couple of months at least, so we'd really appreciate some assistance if someone from the community wanted to step in an help out :) |
It appears the first version of Firefox causing this issue was |
Firefox releases are here. |
I was able to replicate the bug on Ubuntu using |
Something strange is going on with plotly.js/src/lib/svg_text_utils.js Line 106 in 073b327
|
Edge works, firefox does not: import plotly.graph_objects as go
f=go.Figure()
f.update_yaxes(title=dict(text="$log_{10}(D)$", font_size=16))
f.show() JupyterLab: 3.2.0 |
It is likely related to this Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1709251 |
Hi - we are trying to tidy up the stale issues and PRs in Plotly's public repositories so that we can focus on things that are still important to our community. Since this one has been sitting for several years, I'm going to close it; if it is still a concern, please add a comment letting us know what recent version of our software you've checked it with so that I can reopen it and add it to our backlog. Thanks for your help - @gvwilson |
Hi Plotly team, I just recently updated my firefox browser to version 84.0.1 and have been using plotly's (v4.14.1) subplots in Jupyter notebook (v6.0.3) with Python (v3.7.6) for a couple months now without issue. I noticed that with this new version of the browser when I call something like:
The figures do not render properly and when I try to toggle the traces by clicking on the legend, all of the plots shrink and are illegible. This issue seems to be caused whenever I add Latex to the legend str using the name argument in go.Scatter while ALSO using the update command to manually set the width and height of the figure. If I do only one or the other, the behavior seems to go back to normal. It also seems to be unique to Firefox, as I did not have an issue with Chrome when I tested this with the same environment. Hoping this is enough information to create a reproducible example and solve this issue.
The text was updated successfully, but these errors were encountered: