motiondivision / motiondivision/motion
[FEATURE] Manually update animations without `requestAnimationFrame`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 33.7k
- Forks
- 1.4k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 14
Description
Is your feature request related to a problem? Please describe.
Framer Motion's animations stop working in scenarios where window.requestAnimationFrame isn't available.
See https://github.com/pmndrs/react-xr/issues/180 for an example of how this is an issue when using framer-motion or framer-motion-3d in a WebXR immersive session.
Describe the solution you'd like
Expose some way of manually updating animations, so users can pick an appropriate looping mechanism when requestAnimationFrame is unavailable.
Describe alternatives you've considered
n/a
Additional context
GSAP provides an .updateRoot() method for this purpose: https://gsap.com/docs/v3/GSAP/gsap.updateRoot()/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start by tracing where window.requestAnimationFrame drives Framer Motion's animation updates, then review the proposed manual-update API against the GSAP updateRoot() example. Done should provide a documented way for users to advance animations when requestAnimationFrame is unavailable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100