-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Brush rect is flat #1134
Comments
Here is two commits between beta 15 and 16 about the brush :
I will try later this week to give a fiddle demonstrating the problem. By the way, thank's for your availability. |
I've tried to reproduce it in a fiddle but I didn't manage to have the same error. I know that without a reproductible case, it's hard to correct, but the error is still present in the latest releases. |
The commits between those releases are mostly to do with resizing transitions. Not that it's a solution, but does the brush show up if you set Other than that, if you send me a link to my private email (on my github profile) I can debug it confidentially. It takes a lot of time just guessing but it should be easy to track down in the debugger. |
The I know that giving you the access should be easier but it's not my call since we have confidential information on this site. I will ask and let you know. As always, thank's for your availability. |
@paulbriton tracked it down to this line in gBrush.selectAll('.brush rect')
.attr('height', brushHeight()); dc.js/src/coordinate-grid-mixin.js Line 1012 in a27ce29
which used to What's curious is that when I try this in the debugger, it still selects all four child rects, even though selection.selectAll is documented as selecting only descendants. So I think the code is incorrect but may work with some versions of d3 but not others (?) I can't explain otherwise how the use of require would affect this code. |
that often worked thanks @paulbriton for tracking this down! this seems to be a mistake introduced in 354b890 fixes #1134
that often worked thanks @paulbriton for tracking this down! this seems to be a mistake introduced in 354b890 fixes #1134
Thanks @paulbriton, released this in 2.0 beta 31 |
@paulbriton reported on gitter:
Bug is present since beta 16.
The text was updated successfully, but these errors were encountered: