Create a gist now

Instantly share code, notes, and snippets.

What would you like to do?
Reporting an Issue

When reporting an issue, please include a link to a live example. Please use bl.ocks.org or RunKit, or a pull request in the appropriate repository with new unit tests, to demonstrate that the described behavior is not the expected behavior. (The use of JSFiddle, JS Bin, CodePen and other sites is discouraged because they insert additional boilerplate around the test code that interferes with debugging.)

Use only the minimum amount of code necessary to reproduce the unexpected behavior. A good bug report should isolate specific methods that exhibit unexpected behavior and precisely define how expectations were violated. What did you expect the method or methods to do, and how did the observed behavior differ? The more precisely you isolate the issue, the faster I can investigate.

Non-actionable bugs may be temporarily closed until you provide additional information. If you can’t isolate the bug any further, please let me know and I will try to help. However, I beg your patience: I must balance your request against many other responsibilities—fixing other bugs, answering other questions, new features, new 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! 🤗

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