-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Delay and trail conflict on useTransition (v9.0.0-rc3) #1099
Comments
So after a bit of initial investigation, I can see we're creating our trail here:
but how delay is handled is the the animation is
So I can only assume that the trailing time calc think it'll only start a trail at time 0, when in this case it could start at time x. |
So there also seems to be a bit of confusion, we currently don't allow |
This has been released on v9.2.0-beta.4 |
…on (pmndrs#1099) * Exclude null and undefined in log scale validation * Fixed formatting Co-authored-by: Thomas Flanitzer <[email protected]>
Hi there! I ran into an issue while creating a multi-stage transition using react-spring.
🐛 Bug Report
As soon as a delay is placed as a property somewhere in the transition, any trail is immediately disregarded.
To Reproduce
See this CodeSandbox: https://codesandbox.io/s/dank-leftpad-hyvle?file=/src/App.js
If a delay is present on any of
from
,enter
orleave
, any value of trail is disregarded. As soon as all mentions of delay are removed, the trail shows up as normal.Expected behavior
I would expect that a delay and trail could be combined, where a delay precedes the staggered set of items following the trail. The typescript annotations show that both trail and delay can be part of the global config, as well as the individual stages, so I figured this should have been a valid combination. If it is not, that is okay too.
Link to repro (highly encouraged)
https://codesandbox.io/s/dank-leftpad-hyvle?file=/src/App.js
Environment
react-spring
v9.0.0-rc3react
v16.12.0Thanks for making something awesome!
The text was updated successfully, but these errors were encountered: