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

Calling brush.move does not update the internal state's selection #42

Closed
SylvainCorlay opened this issue Feb 28, 2019 · 2 comments
Closed

Comments

@SylvainCorlay
Copy link

When e.g. resizing a figure, we call brush.move on active brush selectors to adjust to the resized figure.

The internal state of the brush is not updated by the call to move causing the interval to jump upon drag.

Our current workaround is to make another call to brush() to update the internal state.

@mbostock
Copy link
Member

I’m not able to reproduce this problem. Here is a working example of brush.move (using transitions, but it works with or without it).

https://observablehq.com/d/a156d984f85884b2

When reporting an issue, please include a link to a live example, preferably as an Observable notebook or as a pull request in the appropriate repository with tests. You should demonstrate that the described behavior is not the expected behavior using the minimum amount of code.

A good bug report should isolate specific methods that exhibit unexpected behavior and define precisely how expectations were violated. What did you expect the method or methods to do, and how did the observed behavior differ? By isolating the issue, you assist the investigation.

Non-actionable bugs may be closed until you provide additional information. If you can’t isolate the bug further, please reply and ask for help. However, please be patient: open-source maintainers have many competing responsibilities—fixing other bugs, answering questions, developing features, writing documentation, etc. Please also consider asking for help on Stack Overflow.

If you have a question about D3’s behavior and want to discuss it with other users, also consider the d3-js Google Group or joining the d3-js Slack.

Thank you! 🤗

@SylvainCorlay
Copy link
Author

Sorry for the inacurate bug description. Now posting a more accurante description of the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants