Skip to content

fix(desktop): don't gate hover affordances on the hover media query #3657

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bradseiler merged 1 commit into from
Jul 30, 2026
+13 −0
Merged

fix(desktop): don't gate hover affordances on the hover media query #3657

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions desktop/src/shared/styles/globals.css
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
@import "tailwindcss";
@import "tw-animate-css";

@import "./globals/scrollbars.css";
@import "./globals/motion.css";
@import "./globals/animations.css";
Expand All @@ -17,3 +18,15 @@
@import "./globals/progress.css";

@config "../../../tailwind.config.js";

/* Tailwind v4 gates `hover:` behind `@media (hover: hover)`. Some Windows
hosts answer that query `false` even with a mouse attached — WebView2 here
reports `hover: none`, `any-pointer: fine: false`, `maxTouchPoints: 10` —
which leaves every hover-revealed control permanently `visibility: hidden`:
member row action menus, sidebar row actions, attachment controls. A bare
`&:hover` trusts the actual hover event instead of the capability query;
Chromium only fires :hover when a real pointer is present.

Must stay below every `@import`: CSS requires `@import` to precede other
at-rules, so placing this above them silently drops the rest of the sheet. */
@custom-variant hover (&:hover);
Loading