@import "tailwindcss";
@import "tw-animate-css";

@import "./globals/scrollbars.css";
@import "./globals/motion.css";
@import "./globals/animations.css";
@import "./globals/composer.css";
@import "./globals/markdown.css";
@import "./globals/theme.css";
@import "./globals/skeleton.css";
@import "./globals/spoilers.css";
@import "./globals/components.css";
@import "./globals/terminal.css";
@import "./globals/utilities.css";
@import "./globals/media-controls.css";
@import "./globals/avatar-framing.css";
@import "./globals/image-lightbox.css";
@import "./globals/video-review.css";
@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);
/* The app persists its selected theme on the root `.dark` class. Use that
   class, rather than the system preference, for every `dark:` utility. */
@custom-variant dark (&:where(.dark, .dark *));