You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<body><scriptsrc="../d3-dispatch/dist/d3-dispatch.js"></script><scriptsrc="../d3-ease/dist/d3-ease.js"></script><scriptsrc="../d3-timer/dist/d3-timer.js"></script><scriptsrc="../d3-selection/dist/d3-selection.js"></script><scriptsrc="../d3-transition/dist/d3-transition.js"></script><script>(asyncfunction(){d3.select("body").append("p").html("start");awaitd3.select("body").transition().duration(1000).end();d3.select("body").append("p").html("end first transition");awaitd3.transition().duration(1000).end();d3.select("body").append("p").html("end second transition")})()</script>
I recommend we revert 91990a1 in favor of #114. A number of inherited selection methods depend on transitions being iterable, such as transition.each and transition.nodes, and they’ll be broken unless transitions are iterable.
d3.transition().duration(1000).end()
results inTypeError: undefined is not a function
by bisection (see below) the offending commit appears to be 60be25f8519ecbdf647059719efcd8dee8e50486
Though the commit is in d3-selection, the issue can be fixed in d3-transition by using that.selection().size() instead of that.size() in
d3-transition/src/transition/end.js
Line 4 in 956f0ae
This is the solution I'll be pushing in d3-transition@two.
The issue is also isolated in https://observablehq.com/d/c976841fa49523ee, but for bisection it was easier to work wih local files and the following test case:
Issue detected by @enjalot
The text was updated successfully, but these errors were encountered: