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
brush.on("end", handle) seems to get raw "mouseup" events #9
Comments
This is appears to be an issue with the use of destructuring assignment rather than import: const {brush, event, select} = d3; The problem here is that d3.event is not a constant: it changes whenever there’s an event. If you save the value of d3.event on load, you should expect it to always be undefined. However, it’s not here because some browsers emulate IE’s global window.event, overriding your If you change your code to refer to http://bl.ocks.org/mbostock/15a9eecf0b29db92f12ca823cfbbce0a You should also be able to |
Okay, tested with I am doing |
Right. The |
So yeah -- I got this working now... Had to in my webpack force it to resolve "d3" to However this is a very annoying problem that I'm sure will catch a lot of users... Perhaps you should build a |
Does webpack not observe jsnext:main? Is there some other magic I can put in the package.json to tell it to find index.js instead of build/d3.js? |
Appears not: webpack/webpack#1979. |
I’ve added some text to the README that will hopefully help avoid this issue:
https://github.com/d3/d3-selection/blob/master/README.md#event |
- configure webpack to use proper entry point for d3: d3/d3-brush#9 - add tooltip with transition to weight chart! - should update css to be in d3.css, not inline styles - should update tooltip to be svg element, not div? Better semantically
http://jsbin.com/rofenucicu/2/edit?js,console,output
I was expecting this to return an "end" event with a
event.selection
The text was updated successfully, but these errors were encountered: