-
Notifications
You must be signed in to change notification settings - Fork 217
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
stop seeing warning about firefox #1650
Comments
|
I haven't been testing nightly FF betas. The only issue I see consistently these days that I think is FF specific is left edit pane doesn't scroll down all the way with mouse with .md and .tex files. Workaround is to use arrow keys to move cursor down. As I recall, there were occasional 100% CPU spins attributed to FF, but I haven't seen one of those for a few weeks. |
There is a ticket with a way to replicate the 100% cpu spins. If it is gone... we can just remove this message. It sounds like it is gone. |
Hardly any CPU spike running latest Firefox Nightly build on OS X and Ubuntu, see #1314. |
Let's keep this open until the fix in Nightly makes it into a Firefox release, then remove the warning. |
Wouldn't we want the warning to appear for older versions of Firefox? |
Or change the warning on older versions of firefox to recommend upgrading. |
Blocked, waiting for firefox release. |
Oh, and there is one more issue with FF. SMC won't let you open a jupyter notebook from firefox because of truncation, issue #1537 |
I'm removing the message and closing. I don't want to mess with complicated (possibly brittle) code for detecting old versions -- there's a ton that can go wrong with each older version, with no end in site. Users not using the latest version are not supported. |
Every time I refresh SMC in Firefox I see the same warning about performance issues "There are major performance issues with Firefox ..." and I have to click to dismiss it. How about a button in the warning that says
Don't show this warning again
?The text was updated successfully, but these errors were encountered: