Use d3.event.timeStamp instead of Date.now?

[mbostock]

That way, if multiple transitions are started independently during the response to an event, they are guaranteed to be concurrent.

However, we’d have to fallback to Date.now if d3.event is undefined. And we’d probably want to use the sourceEvent rather than d3.event. Although, we haven’t implemented any behaviors yet (drag, zoom, brush), so currently there is no difference.

[mbostock]

Also note that requestAnimationFrame passes the callback the current time, and so does d3-timer; we could use that reference time even when there isn’t a user event.

[mbostock]

I don’t plan on implementing this in the near future, so closing.