motiondivision / motiondivision/motion
[BUG] Animation Dosent work ( A Transform:none style adding 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
<nav id="nav-bar" class="fixed left-0 top-0 z-50 grid h-24 w-full grid-cols-[0.8fr,2fr,1fr] grid-rows-1 place-content-start bg-background/90 px-6 text-sm text-foreground shadow-sm" style="transform: none;"></nav>
Motion Components add a transform:none style, Not all the motion components specificlly the ones that has 'fixed' position ( in my project )
initial={{ translateY: "-100%", scaleY: 0.8 }}
animate={{
translateY: 0,
scaleY: 1,
}}
transition={{
duration: 0.4,
delay: 0.1,
type: "spring",
stiffness: 30,
}}
id="nav-bar"
className="fixed left-0 top-0 z-50 grid h-24 w-full grid-cols-[0.8fr,2fr,1fr] grid-rows-1 place-content-start bg-background/90 px-6 text-sm text-foreground shadow-sm"
>```
`` `@tailwind base;
@tailwind components;
@tailwind utilities;
@layer base {
body {
@apply min-h-screen bg-background/95 font-poppins text-foreground selection:bg-foreground/30;
}
main {
@apply relative h-full w-full pt-24;
}
}
This isnt a motion.nav self closed tag there are items but I only added the nav ,
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 the motion.nav example and inspect how Motion components generate inline transform styles, especially for elements using fixed positioning. Reproduce the reported transform:none output, then add a regression test showing the expected transform behavior and verify that the unwanted style is no longer emitted.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100