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

[BUG] Property-specific transitions break parent orchestration #1081

Closed
marcbouchenoire opened this issue Apr 1, 2021 · 0 comments
Closed
Labels
bug Something isn't working

Comments

@marcbouchenoire
Copy link

Describe the bug

Setting transition to be multiple property-specific transitions (e.g. opacity and scale) rather than a single transition breaks inherited orchestration like staggerChildren.

bug.mp4

CodeSandbox reproduction

https://codesandbox.io/s/framer-motion-staggerchildren-bug-b6qxb?file=/src/index.tsx

4. Steps to reproduce

Steps to reproduce the behavior:

  1. Go to index.tsx
  2. Follow the two comments to see the two cases: single transition (working), object of transitions (bug)

5. Expected behavior

staggerChildren delays any child variant transition, whether it's set from a single transition or a property-specific one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants