-
Notifications
You must be signed in to change notification settings - Fork 389
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
Panning is very jerky with Firefox Quantum - possibly interaction with d3.js? #277
Comments
Hi @gramster, Thank you for the report. One solution could be to set the Most probably that's a performance issue, and I don't think there is much we could do. I'll keep it open as a reference for performance. Some context on technique:
Similar issues:
Better performance using alternative libraries:
|
I am using the latest version, together with Spyre (https://github.com/adamhajari/spyre). Basically I am trying to create a dashboard with Spyre that allows me to control some parameters, that I then use to generate a graph with graphviz, and then I convert that to an svg and display it. The graphs can be quite large so I want the pan and zoom functionality.
It's working great in Chrome and Safari. In FireFox Quantum (57.0.4) it is terrible though. Panning on my Mac is configured to use 3 finger drag, although I don't think that should be an issue. What happens when I start panning is the graph will move slightly and then stop moving. The amount is variable; sometimes I get a decent amount, but often just a little bit and I have to re-pan multiple times to get the movement I want.
The tiger demos work fine though, so its something related to my situation.
Spyre doesn't add too much but it does pull in d3.js, so that may be having an effect. I want to check if there are other event handlers that could be interfering but its not obvious how to do this in Firefox; the debug tools don't show anything that I can see (but I don't see an explicit event handlers section like Chrome has).
This isn't a big problem for me; I'll just use Chrome. But I thought it was worth reporting.
The text was updated successfully, but these errors were encountered: