Skip to content
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

Nodes layout zoom sensitivity differs between Firefox and Chrome #2787

Closed
fbarl opened this issue Aug 2, 2017 · 0 comments · Fixed by #2812
Closed

Nodes layout zoom sensitivity differs between Firefox and Chrome #2787

fbarl opened this issue Aug 2, 2017 · 0 comments · Fixed by #2812
Assignees
Labels
chore Related to fix/refinement/improvement of end user or new/existing developer functionality component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer

Comments

@fbarl
Copy link
Contributor

fbarl commented Aug 2, 2017

See #2768. As long as we are using d3-zoom, this will be a problem. However, we could make ZoomableCanvas use the same triggers and constants as TimeTravelTimeline does for zooming, which would make the sensitivity consistent between the browsers and the zooming behaviour consistent between different controls in our app (and would also give us more control over zooming).

@fbarl fbarl added accuracy Incorrect information is being shown to the user; usually a bug component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer labels Aug 2, 2017
@fbarl fbarl self-assigned this Aug 2, 2017
@rade rade added chore Related to fix/refinement/improvement of end user or new/existing developer functionality and removed accuracy Incorrect information is being shown to the user; usually a bug labels Aug 2, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chore Related to fix/refinement/improvement of end user or new/existing developer functionality component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants