-
Notifications
You must be signed in to change notification settings - Fork 354
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
Applying zoom to page body causes X-Grid-Focus to become disconnected from cursor #3273
Comments
Worth noting the same issue happens with transform-scale and its implementation in various browsers. |
It sounds like #2095. |
Disconnected as in the x coordinate of the x-grid-focus is not the x coordinate of the cursor. The coordinate space of the screen is being projected down into a smaller coordinate space of the chart. If you notice in the image my cursor is ~400px to the right of the x-grid-focus Also when I refer to "zoom: 0.75;" I'm referring to zoom being added to my website style sheet, not the zoom function within billboard.js. Thought I should clarify. |
I missed the condition you had written first:
I think in general it's hard for the library to resolve the issue Dirty workaround ?
|
That should get me where I need to go. Thank you! |
When I add "zoom: 0.75;" to my style sheet, all the elements scale correctly; but the x-grid-focus and tooltip become disconnected from the client cursor. It behaves like the x-grid-focus and cursor are not in the same coordinate space. I've tried various combinations of zooms and transform scales in both my style sheet and the billboard style sheet with no success.
Let me know if there's anything I should try or if this sounds like a genuine bug. I'm happy to provide anything that would help solve the issue.
Below is a screenshot of the issue I'm having. The X is almost exactly where my cursor was in that shot. The x-grid-focus aligns correctly on the left side of the chart, indicating it aligns at 0, but the disparity grows as you move right.
The text was updated successfully, but these errors were encountered: