Skip to content

fix: improve mock button hover contrast#19

Merged
yepzdk merged 1 commit intomainfrom
feature/fix-mock-button-hover-contrast
Apr 29, 2026
Merged

fix: improve mock button hover contrast#19
yepzdk merged 1 commit intomainfrom
feature/fix-mock-button-hover-contrast

Conversation

@yepzdk
Copy link
Copy Markdown
Contributor

@yepzdk yepzdk commented Apr 29, 2026

Summary

  • The Åbn prototypen mock buttons across project pages had a near-invisible label on hover — VitePress's default .vp-doc a link styles were outweighing .mock-button on specificity, so the brand-colored text stayed on top of the brand-colored hover background.
  • Raised specificity in docs/.vitepress/theme/custom.css with a .vp-doc a.mock-button selector so white text and no underline actually apply on hover.

Screenshot

Screenshot 2026-04-29 at 12 05 46 Efter: Screenshot 2026-04-29 at 12 22 34

Test plan

  • Run task dev (or npm run docs:dev)
  • Open a project page that has a prototype button (e.g. Opkrævningsoverblik, Roboway, deltag.aarhus.dk)
  • Hover the Åbn prototypen ↗ button and confirm the label is white and legible against the teal background
  • Verify the resting state is unchanged (brand-colored text, no underline)
  • Check both light and dark mode

Generated with Claude Code

The "Åbn prototypen" button text was nearly invisible on hover because
VitePress's default `.vp-doc a` link styles outweighed `.mock-button`
on specificity, leaving the label brand-colored on a brand-colored
background. Raise specificity so white text and no underline win on hover.

Co-authored-by: Claude <noreply@anthropic.com>
@yepzdk yepzdk force-pushed the feature/fix-mock-button-hover-contrast branch from 2346b8a to 55d0eba Compare April 29, 2026 10:21
@yepzdk yepzdk requested a review from jeppekroghitk April 29, 2026 10:22
@yepzdk yepzdk merged commit a9514b9 into main Apr 29, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants