You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 04c4d8e
Browse filesBrowse the repository at this point in the historyBrowse files
fix(styles): restore transition timing Tailwind was silently dropping
`tailwindcss-animate` adds a `duration-*` utility for `animation-duration`,
which collides with core's `transition-duration`. For a named value Tailwind
emits both rules, but for an arbitrary value it cannot pick one — so it drops
the class entirely and warns.
The result is 52 usages across 13 files that produced **no CSS at all**.
Elements marked `transition-transform duration-[1700ms]
ease-[cubic-bezier(0.22,1,0.36,1)]` had neither a duration nor an easing
function: they snapped instead of animating. Most of it is the landing hero.
Verified by compiling the stylesheet on both sides:
transition-duration: 1700ms before=0 after=1
transition-duration: 420ms before=0 after=1
transition-duration: 175ms before=0 after=1
transition-timing-function: cubic-bezier(0.22,1,0.36,1) before=0 after=1
transition-timing-function: cubic-bezier(0.23,1,0.32,1) before=0 after=1
The stylesheet grows 1,425 bytes — exactly the rules that were missing — and
the 16 ambiguity warnings on every dev start go to zero.
Every usage is in a transition context (`transition-opacity`,
`transition-transform`, `transition-[...]`); none sits alongside an `animate-*`
utility, so `transition-duration`/`transition-timing-function` is the right
half of the collision in all 52 cases.
Copy file name to clipboardExpand all lines: apps/sim/app/(landing)/components/landing-preview/components/landing-preview-chat/landing-preview-chat.tsx
0 commit comments