AuthorD3.js conflict Posts
I’m using D3.js together with various jQWidgets components and for the most part it is working fine. However, when I use jqxDragDrop I get an issue with events triggering on D3 components.
Edit: the link to jsfiddle isn’t showing, so here it is again: http://jsfiddle.net/6oLdp6z0/
The first div is a brushable area that should allow dragging to select an area. If I call jqxDragDrop() the mouseup is no longer triggered on the brush and it gets stuck in a “brushing” state. Simply removing the jqxDragDrop() call will restore it to normal function.
Interestingly, it works fine when using a touch interface or emulated touch in Chrome.
Is it possible to get these components working together?
- This topic was modified 5 years, 3 months ago by jimmux. Reason: Link not showing
we do not support a library called D3 and never tested our widgets with it. If that libary handles events and prevents them to be handled from other plugins, then there’s nothing we can do. You may find a various libraries which integrate well with our widgets on the Documentation page.
I’m evaluating usage of jQWidgets and a possible purchase of a license.
Conflicts with the popular D3JS library is a major concern to me.
In regards to the specific and very clear reproduction of the issue presented above, using jsfiddle, it looks like adding jqwidgets affects D3JS, not d3js affecting jqwidgets.
“If that libary handles events and prevents them to be handled from other plugins,”
It seems that once jqwidgets is disabled the drag drop events return to function with D3JS, which suggests that the problem might be jqWidgets blocking the event.
Could you look at that problem and provide an explanation?
The answer remains the same. We do not support this library. D3 works without jqxDragDrop on the page. The same is valid however for jqxDragDrop whcih works without D3. As we do not support it, we do not know what is the issue. In case we add a support for it in the future, we will most likely look into this, too.
You must be logged in to reply to this topic.