motiondivision / motiondivision/motion
[BUG] ScaleZ doesn't get applied to the motion component
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 33.7k
- Forks
- 1.4k
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 14
Description
[BUG explanation] :
When adding styles through the initial/animate directly or even through variants all the styles get applied other than the scaleZ.
Even when rotateZ and translateZ get applied the scaleZ doesn't.
[Code sandbox] :
CodeSandbox
notice when you inspect the element the scaleZ is the only property that isn't there.
[Steps to reproduce]:
Add scaleZ to any motion component.
[Expected behavior]:
The element should have scaleZ applied just like scaleX and scaleY.
[Screenshots] :
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
Start with src/FramerComponent.js in the linked CodeSandbox and reproduce the issue by comparing scaleZ with scaleX, scaleY, rotateZ, and translateZ on a motion component. Done means scaleZ is applied to the inspected element in the same way as the other scale properties.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100