8000 Transition must evaluate new values immediately. · Issue #37 · d3/d3-transition · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Transition must evaluate new values immediately. #37

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

Closed
mbostock opened this issue Feb 23, 2016 · 0 comments
Closed

Transition must evaluate new values immediately. #37

mbostock opened this issue Feb 23, 2016 · 0 comments
Assignees

Comments

@mbostock
Copy link
Member

Currently transition.{attr,style,text,…} are built on transition.tween, and they don’t evaluate the new value until the tween is initialized. That’s bad; many examples (such as this one) rely on synchronous evaluation of transition.attr and the like, so that external state can be modified during the initialization of a transition.

I’m not suggesting we change transition.{attrTween,styleTween,tween,…}: those can’t be evaluated until the transition starts, by design. By the transition methods that only compute the destination value must be evaluated earlier.

@mbostock mbostock self-assigned this Feb 23, 2016
@mbostock mbostock changed the title transition.{attr,style,text,…} must evaluate the new value immediately. Transition must evaluate new values immediately. Feb 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant
0