@import "tailwindcss"; /* Inter, self-hosted (#1460). Bambuddy is a local-first, offline-capable PWA; pulling the font from fonts.googleapis.com at runtime broke the install on Android (CSP-blocked cross-origin fetch) and meant the UI couldn't render offline. These are the variable woff2 files Google Fonts serves — one file covers every weight via the variable axis, so font-weight is a 100-900 range. Files live in frontend/public/fonts/ and are served same-origin. */ @font-face { font-family: 'Inter'; font-style: normal; font-weight: 100 900; font-display: swap; src: url('/fonts/inter-latin.woff2') format('woff2'); unicode-range: U+0000-00FF, U+0131, U+0152-0153, U+02BB-02BC, U+02C6, U+02DA, U+02DC, U+0304, U+0308, U+0329, U+2000-206F, U+20AC, U+2122, U+2191, U+2193, U+2212, U+2215, U+FEFF, U+FFFD; } @font-face { font-family: 'Inter'; font-style: normal; font-weight: 100 900; font-display: swap; src: url('/fonts/inter-latin-ext.woff2') format('woff2'); unicode-range: U+0100-02BA, U+02BD-02C5, U+02C7-02CC, U+02CE-02D7, U+02DD-02FF, U+0304, U+0308, U+0329, U+1D00-1DBF, U+1E00-1E9F, U+1EF2-1EFF, U+2020, U+20A0-20AB, U+20AD-20C0, U+2113, U+2C60-2C7F, U+A720-A7FF; } /* Enable class-based dark mode for Tailwind v4 */ @custom-variant dark (&:where(.dark, .dark *)); /* Hover-capable pointer only (#2865). Tailwind v4 compiles `hover:` AND `group-hover:` inside `@media (hover: hover)`, so on a touch-only device the reveal rule is never applied at all — a control written as `opacity-0 group-hover:opacity-100` stays invisible forever, which is how the project card's action menu became unreachable on a phone. Gating the HIDING half on this variant is what fixes it: with no hover-capable pointer the element simply keeps its natural opacity. Same query the history thumbnail preview already uses further down. */ @custom-variant can-hover (@media (hover: hover) and (pointer: fine)); /* Restore the pointer cursor on interactive controls (#2791). Tailwind v3's Preflight set `button { cursor: pointer }`; v4 dropped it to match the browser default of `cursor: default`, so every button in the app looked unclickable unless someone remembered to add `cursor-pointer` by hand. Only a handful of the ~930 buttons did, which is why the UI felt inconsistent rather than uniformly wrong. This lives in `base`, the lowest of Tailwind's cascade layers, so the `cursor-not-allowed` / `disabled:cursor-*` utilities dotted around the codebase still win. The `:not(:disabled)` guard covers the elements that are disabled without also carrying such a utility. */ @layer base { button:not(:disabled), select:not(:disabled), summary, input[type="checkbox"]:not(:disabled), input[type="radio"]:not(:disabled), [role="button"]:not([aria-disabled="true"]) { cursor: pointer; } } @theme { /* Accent colors - use CSS variables for theming */ --color-bambu-green: var(--accent); --color-bambu-green-light: var(--accent-light); --color-bambu-green-dark: var(--accent-dark); /* Semantic status colors - fixed, don't change with accent */ --color-status-ok: var(--status-ok); --color-status-error: var(--status-error); --color-status-warning: var(--status-warning); /* Theme-aware colors via CSS variables */ --color-bambu-dark: var(--bg-primary); --color-bambu-dark-secondary: var(--bg-secondary); --color-bambu-dark-tertiary: var(--bg-tertiary); --color-bambu-gray: var(--text-muted); --color-bambu-gray-light: var(--text-secondary); --color-bambu-gray-dark: var(--text-tertiary); } /* ============================================ BASE DEFAULTS ============================================ */ html { font-size: 14.4px; } :root { /* Default accent color (green) */ --accent: #00ae42; --accent-light: #00c64d; --accent-dark: #009438; /* Semantic status colors - these never change with accent theme */ --status-ok: #22c55e; /* green-500 - always green for success/online/ok */ --status-error: #ef4444; /* red-500 - always red for error/offline/failed */ --status-warning: #f59e0b; /* amber-500 - always amber for warnings */ /* Default light mode background (neutral) */ --bg-primary: #f5f5f5; --bg-secondary: #ffffff; --bg-tertiary: #e5e5e5; --text-primary: #1a1a1a; --text-secondary: #4a4a4a; --text-muted: #6b6b6b; --text-tertiary: #808080; --border-color: #d4d4d4; /* Default style (classic) */ --card-shadow: 0 2px 8px rgba(0, 0, 0, 0.08); --glow-color: transparent; /* Tell the browser which appearance the page is in, so the parts of a form control it draws itself follow the theme. Bambuddy themes by swapping CSS variables under a `.dark` class, which the browser cannot see: without this declaration it assumes light and paints every native widget internal that way -- number-input steppers, the date picker's calendar button and its popup, ` paints its value inside a fixed inner padding and its own border, so at 14px the colour reads as a dot inside a pale ring rather than as the round swatch it replaced. These reset both so the element is nothing but the colour. */ .slice-colour-swatch { -webkit-appearance: none; -moz-appearance: none; appearance: none; overflow: hidden; } .slice-colour-swatch::-webkit-color-swatch-wrapper { padding: 0; } .slice-colour-swatch::-webkit-color-swatch { border: none; border-radius: 999px; } .slice-colour-swatch::-moz-color-swatch { border: none; border-radius: 999px; }