Fix transition-all on website card (website-card.tsx:193)
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 88/100
- Issue type
- Refactor
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- tailwindcss, typescript
- Domain
- frontend
Research direction
The change is on line 193 of apps/dashboard/app/(main)/websites/_components/website-card.tsx, where the class list uses transition-all. Read the hover classes on that element first, since the issue says only the border color changes on hover. Replace transition-all with transition-colors and keep the duration and easing. Done when the hover border transition still plays and no other classes changed.
Written by the indexing model from the issue text.
Description
What
apps/dashboard/app/(main)/websites/_components/website-card.tsx:193 uses transition-all duration-300 ease-in-out on the website card.
Why it matters
transition-all animates every CSS property — width, height, colors, shadows, filters, everything. Animating expensive or never-changing properties on hover causes jank and wastes browser work.
Fix
Replace it with only the property that actually changes on hover (the border color):
- transition-all duration-300 ease-in-out
+ transition-colors duration-300 ease-in-out
group-hover:z-50 changes z-index, which doesn't animate; group-hover:border-primary/60 is a border-color change covered by transition-colors.
- Dominant language
- TypeScript
- Stars
- 1.2k
- Forks
- 227
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 249
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from databuddy-analytics/Databuddy
-
fix(basket): redact sensitive params and keep query separators in batched outgoing link hrefsPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
databuddy-analytics/Databuddy#1143 ·
Maintainers usually reply within 1 day
-
refactor(home): standardize "Install tracking" empty state using EmptyState componentPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
databuddy-analytics/Databuddy#1138 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
databuddy-analytics/Databuddy#1131 · 1 reaction ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
databuddy-analytics/Databuddy#1126 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
databuddy-analytics/Databuddy#1108 ·
Maintainers usually reply within 1 day
All issues in databuddy-analytics/Databuddy
Similar issues
-
Sequências em espanhol: «Atualizado em», a aba «Fila» e o valor 'pause' ainda saem em portuguêsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
melgarafael/DeskcommCRM#3104 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug service: webapp
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Ocelot-Social-Community/Ocelot-Social#10684 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nicobailon/pi-subagents#2978 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
getsentry/sentry-conventions#732 · 1 comment ·
Maintainers usually reply within 1 day