Skip to content
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

Fix #27 - inaccurate timeout delay. #28

Merged
merged 1 commit into from
Sep 3, 2017
Merged

Conversation

mbostock
Copy link
Member

@mbostock mbostock commented Aug 4, 2017

If timers are expensive, then by the time we sleep, the current time may have advanced substantially from the clockNow computed on wake. Therefore we must recompute the current time before scheduling the timeout.

If timers are expensive, then by the time we sleep, the current time may have
advanced substantially from the `clockNow` computed on wake. Therefore we must
recompute the current time before scheduling the timeout.
@magjac
Copy link

magjac commented Aug 9, 2017

Thanks for fixing this so quickly! Now it works as expected 😄.

Will you be making a release of it any time soon? I just published the d3-graphviz plugin. The demos contain workarounds for this issue that I would like to remove.

If you're interested, the demos are here:

@magjac
Copy link

magjac commented Sep 3, 2017

Is there any particular reason this didn't make it into d3/d3 v4.10.1? Anything I can do to help?

@mbostock
Copy link
Member Author

mbostock commented Sep 3, 2017

No particular reason—I just forgot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants