| 1 |
/** |
| 2 |
* OpenStation — CSS Custom Properties. |
| 3 |
* |
| 4 |
* All design tokens for the desktop shell, carrying the OpenStation |
| 5 |
* brand: https://nuriapenya.github.io/open-station-brand/ |
| 6 |
* |
| 7 |
* ## The palette |
| 8 |
* |
| 9 |
* Pulse #f252fc neon identity accent |
| 10 |
* Nebula #ec9bff soft identity accent |
| 11 |
* Sirius #c2f1f1 aqua contrast accent |
| 12 |
* Starlight #fffbff lightest — primary text on the station |
| 13 |
* Void #0c0b0f darkest — the base everything sits on |
| 14 |
* Obsidian #1a1721 surfaces: window bodies, cards, rows |
| 15 |
* |
| 16 |
* Shade ramp, Void to Starlight, for text hierarchy and lines: |
| 17 |
* Astro #33303a · Silver #4d4a52 · Pewter #66636b · |
| 18 |
* Osmium #99969c · Ash #b3afb5 · Cloud #ccc8ce · Mist #e6e2e6 |
| 19 |
* |
| 20 |
* The brand's own composition rule, followed here literally: "Void as |
| 21 |
* the base, Obsidian for surfaces, Pulse and Nebula for identity |
| 22 |
* moments, Sirius and Starlight for contrast, the Shade palette for |
| 23 |
* text hierarchy and lines, meshes reserved for hero surfaces." |
| 24 |
* |
| 25 |
* ## Why these are declared at all |
| 26 |
* |
| 27 |
* Every rule in the tree reads its token as |
| 28 |
* `var( --token, <literal> )`, and those literals are the look the |
| 29 |
* shell had before the brand: WordPress-admin greys and blues. They |
| 30 |
* are still there, still correct, and still what renders if this file |
| 31 |
* fails to load. Declaring the tokens here is what puts the station on |
| 32 |
* top of them — one declaration retints every surface that reads it. |
| 33 |
* |
| 34 |
* The way back is a theme, not an edit: **Desktop Mode (Legacy)** |
| 35 |
* (`assets/desktop-themes/legacy/theme.json`) is a frozen snapshot of |
| 36 |
* those pre-brand literals, and picking it in OS Settings → Themes |
| 37 |
* restores the old look wholesale. A desktop theme's compiled selector |
| 38 |
* weighs (0,2,0) against this file's `:root` (0,1,0) and loads after |
| 39 |
* it, so any theme — Legacy or a third party's — outranks everything |
| 40 |
* below. |
| 41 |
* |
| 42 |
* ## Semantic colours |
| 43 |
* |
| 44 |
* The brand defines no status palette, so danger / success / warning / |
| 45 |
* info are derived rather than quoted: the hues the shell already used, |
| 46 |
* lifted until they carry on a Void-to-Obsidian background, and where |
| 47 |
* the brand does have a colour that means the right thing it is used |
| 48 |
* instead — Sirius for info, and Holomesh's mint and warm for success |
| 49 |
* and warning. |
| 50 |
*/ |
| 51 |
|
| 52 |
/* |
| 53 |
* ---- Typefaces ------------------------------------------------- |
| 54 |
* |
| 55 |
* Geist and Geist Mono, the brand faces, self-hosted from |
| 56 |
* `assets/fonts/` under the SIL Open Font License 1.1 (the licence |
| 57 |
* text ships beside them in `OFL.txt`). Both are VARIABLE fonts: one |
| 58 |
* file covers 100–900, which is why a whole typographic scale costs |
| 59 |
* ~70 kB per family rather than one file per weight. |
| 60 |
* |
| 61 |
* `font-display: swap` paints fallback text immediately and swaps when |
| 62 |
* the face arrives — on admin chrome that is almost always right, |
| 63 |
* where `block` would hide every dock label until the download lands. |
| 64 |
* |
| 65 |
* The `url()`s are relative to THIS stylesheet, which is what keeps |
| 66 |
* them correct however the plugin directory is renamed or wherever it |
| 67 |
* is symlinked from. |
| 68 |
*/ |
| 69 |
@font-face { |
| 70 |
font-family: 'Geist'; |
| 71 |
src: url('../fonts/Geist-Variable.woff2') format('woff2'); |
| 72 |
font-weight: 100 900; |
| 73 |
font-style: normal; |
| 74 |
font-display: swap; |
| 75 |
} |
| 76 |
|
| 77 |
@font-face { |
| 78 |
font-family: 'Geist Mono'; |
| 79 |
src: url('../fonts/GeistMono-Variable.woff2') format('woff2'); |
| 80 |
font-weight: 100 900; |
| 81 |
font-style: normal; |
| 82 |
font-display: swap; |
| 83 |
} |
| 84 |
|
| 85 |
/* |
| 86 |
* ---- Registered, so "undeclared" never means transparent --------- |
| 87 |
* |
| 88 |
* The scope note below keeps this palette out of iframe documents on |
| 89 |
* purpose: an admin page inside a window renders with the values its |
| 90 |
* own stylesheets were written with. That promise has one hole CSS |
| 91 |
* digs by itself — a stylesheet that consumes |
| 92 |
* `var(--wp-admin-theme-color)` with no fallback, in a document where |
| 93 |
* nothing declares it, does not fall back to an earlier declaration |
| 94 |
* in the cascade. An unresolved `var()` is invalid at computed-value |
| 95 |
* time, so the property computes to `initial` — and an unregistered |
| 96 |
* custom property's initial value is the guaranteed-invalid value, |
| 97 |
* which for a `background` means transparent. Core's own scheme files |
| 98 |
* declare the property, but a third-party admin scheme that consumes |
| 99 |
* it without declaring it renders `.button-primary` white-on-white |
| 100 |
* inside every chromeless window (#702). |
| 101 |
* |
| 102 |
* Registering the property gives "undeclared" a real answer: |
| 103 |
* WordPress's default admin colour, the same value Core's fallbacks |
| 104 |
* reach for. Declarations are untouched — a scheme, the palette |
| 105 |
* below, or the accent picker's inline style all keep winning exactly |
| 106 |
* as before. Registration only decides what the absence of all of |
| 107 |
* them computes to. |
| 108 |
*/ |
| 109 |
@property --wp-admin-theme-color { |
| 110 |
syntax: "<color>"; |
| 111 |
inherits: true; |
| 112 |
initial-value: #3858e9; |
| 113 |
} |
| 114 |
|
| 115 |
/* |
| 116 |
* ---- Scope: the shell document, and nothing else ----------------- |
| 117 |
* |
| 118 |
* `body.os-active` rather than `:root`, and that is |
| 119 |
* load-bearing rather than tidy. |
| 120 |
* |
| 121 |
* This stylesheet is a dependency of `chromeless.css`, so it also |
| 122 |
* loads INSIDE every iframe window — a real `wp-admin` document. A |
| 123 |
* palette on `:root` would reach that document and repaint WordPress's |
| 124 |
* own UI: `--wp-admin-theme-color` alone would turn Core's primary |
| 125 |
* buttons, links and focus rings across every admin screen, with |
| 126 |
* white button text landing on a colour it was never contrast-tested |
| 127 |
* against. |
| 128 |
* |
| 129 |
* Iframe documents carry `body.os-chromeless` instead, so |
| 130 |
* they match nothing here and every rule in the tree falls back to the |
| 131 |
* literal it was always written with — the WordPress-admin values. |
| 132 |
* **An admin page inside a window looks exactly as it does outside |
| 133 |
* one.** That is deliberate: the station is the chrome around the |
| 134 |
* page, not a reskin of the page. |
| 135 |
* |
| 136 |
* Specificity: (0,1,1). A desktop theme compiles to |
| 137 |
* `body.os-desktop-theme-<slug>`, also (0,1,1) on the same |
| 138 |
* element, and its stylesheet declares `os-variables` as a |
| 139 |
* dependency — so it always prints after this file and wins the tie. |
| 140 |
* Do not remove that dependency; see the note in |
| 141 |
* `openstation_enqueue_desktop_theme_style()`. |
| 142 |
*/ |
| 143 |
body.os-active { |
| 144 |
/* MIO's conversation follows desktop themes through these public tokens. */ |
| 145 |
--os-mio-chat-bg: var(--os-ui-modal-bg, #15151e); |
| 146 |
--os-mio-chat-fg: var(--os-ui-modal-text, #f4f4fb); |
| 147 |
--os-mio-chat-muted: var(--os-ui-modal-text-muted, #b4b4c6); |
| 148 |
--os-mio-chat-hover-bg: color-mix(in srgb, var(--os-mio-chat-bg, #fff) 90%, var(--os-mio-chat-fg, #1d2327)); |
| 149 |
--os-mio-chat-border: color-mix(in srgb, var(--os-ui-accent, #a855f7) 40%, transparent); |
| 150 |
--os-mio-chat-user-bg: color-mix(in srgb, var(--os-ui-accent, #3f6dff) 15%, transparent); |
| 151 |
--os-mio-chat-glow: color-mix(in srgb, var(--os-ui-accent-dim, #ff4fd8) 10%, transparent); |
| 152 |
--os-mio-launcher-bg: color-mix(in srgb, var(--os-mio-chat-bg, #fff) 62%, transparent); |
| 153 |
--os-mio-callout-bg: var(--os-mio-chat-bg, #15151e); |
| 154 |
--os-mio-callout-fg: var(--os-mio-chat-fg, #f4f4fb); |
| 155 |
--os-mio-callout-border: color-mix(in srgb, var(--os-ui-accent-dim, #a855f7) 32%, transparent); |
| 156 |
--os-mio-chat-radius: max(18px, var(--os-window-radius, 22px)); |
| 157 |
|
| 158 |
/* |
| 159 |
* ---- Desk -------------------------------------------------- |
| 160 |
* |
| 161 |
* `Space`, the brand's quiet deep-space backdrop: a linear |
| 162 |
* gradient from near-black through to a faint violet horizon. |
| 163 |
* |
| 164 |
* Note this is the desk's CSS default, not usually what you see: |
| 165 |
* the wallpaper layer writes the ACTIVE wallpaper into this same |
| 166 |
* property as an inline style, and the shipped default is the |
| 167 |
* `Galaxy` artwork (`includes/wallpapers.php`). This value is what |
| 168 |
* paints before that runs, and for anyone whose wallpaper is |
| 169 |
* unavailable. |
| 170 |
*/ |
| 171 |
--os-bg: linear-gradient(160deg, #010101 0%, #111114 58%, #1e1d23 100%); |
| 172 |
/* |
| 173 |
* Flat colour painted on the shell itself, behind every other |
| 174 |
* layer including the wallpaper. |
| 175 |
* |
| 176 |
* The shell is `position: fixed` over the classic admin page, and |
| 177 |
* that page is WHITE. Anything that leaves a layer unpainted for a |
| 178 |
* single frame — a canvas wallpaper's context being disturbed, the |
| 179 |
* compositor re-rasterising after a large GPU layer goes away — |
| 180 |
* shows it. This is the floor that makes that impossible: the worst |
| 181 |
* a dropped frame can now look like is Void. |
| 182 |
* |
| 183 |
* Deliberately a solid rather than `--os-bg`: it is never |
| 184 |
* seen when things are working, so it should cost one flat fill, |
| 185 |
* not a second gradient rasterisation on every shell repaint. |
| 186 |
*/ |
| 187 |
--os-backstop: #0c0b0f; |
| 188 |
--os-area-inset: 0; |
| 189 |
|
| 190 |
/* |
| 191 |
* ── The icon grid ──────────────────────────────────────────── |
| 192 |
* |
| 193 |
* ONE grid, everywhere placements are laid out: the wallpaper, |
| 194 |
* folder windows, and every canvas in the site folder. Before |
| 195 |
* these tokens each surface carried its own pitch and its own |
| 196 |
* tile width, and the two drifted apart — the desktop ended up |
| 197 |
* with an 88px tile in a 96px cell whose 8px of air the tile's |
| 198 |
* own padding ate, so icons touched edge to edge while the site |
| 199 |
* folder had 20px between them. |
| 200 |
* |
| 201 |
* The cell is derived, never declared: `cell = tile + gap`. A |
| 202 |
* gap you can see is the whole point, so it is the number that |
| 203 |
* gets tuned; the pitch follows. |
| 204 |
* |
| 205 |
* The TypeScript side mirrors these in `src/desktop-files/grid.ts` |
| 206 |
* (layout maths can't read CSS), and |
| 207 |
* `tests/vitest/grid-metrics.test.ts` parses this file to prove |
| 208 |
* the two agree. Change a number here and that test tells you |
| 209 |
* exactly which constant to move with it. |
| 210 |
*/ |
| 211 |
--os-tile-w: 88px; |
| 212 |
/* |
| 213 |
* A FIXED height, and it has to fit the tallest a tile can get: |
| 214 |
* 8px padding + 48px icon well + 6px gap + two clamped label |
| 215 |
* lines (2 × 12px × 1.2 = 28.8px) + 8px padding = 98.8px, so |
| 216 |
* 104px with a little slack for font metrics. |
| 217 |
* |
| 218 |
* Fixed rather than minimum because the selection ring is drawn |
| 219 |
* around the tile box: let the box follow its label and a row of |
| 220 |
* selected icons is a ragged run of different-height rectangles, |
| 221 |
* one per label that happened to wrap. |
| 222 |
*/ |
| 223 |
--os-tile-h: 104px; |
| 224 |
--os-grid-gap-x: 20px; |
| 225 |
--os-grid-gap-y: 16px; |
| 226 |
/* Gutter from the top / inline-start edge of any icon canvas. */ |
| 227 |
--os-grid-padding: 16px; |
| 228 |
/* |
| 229 |
* Image-led sections opt into a bigger tile (`tileSize: 'large'`) |
| 230 |
* — a shop's products read as a catalogue, not a file list. Same |
| 231 |
* gaps, bigger tile. |
| 232 |
*/ |
| 233 |
--os-tile-w-large: 132px; |
| 234 |
--os-tile-h-large: 160px; |
| 235 |
|
| 236 |
/* Window chrome — Obsidian body inside a Starlight hairline. */ |
| 237 |
--os-window-bg: #1a1721; |
| 238 |
--os-window-border: rgba(255, 251, 255, 0.12); |
| 239 |
/* |
| 240 |
* Window corner. Softer than the 8px the shell carried before, so |
| 241 |
* a window reads as an object on the desk rather than a panel |
| 242 |
* pinned to it. |
| 243 |
* |
| 244 |
* The tab strip's own radius is deliberately NOT tied to this one. |
| 245 |
* A tab is 30px tall, so a corner anywhere near this size eats the |
| 246 |
* whole straight edge and turns the tab into a capsule — it stops |
| 247 |
* reading as a folder tab attached to the page, which is the one |
| 248 |
* thing the tab has to say. `--os-tabs-radius` stays smaller and |
| 249 |
* independent on purpose. |
| 250 |
*/ |
| 251 |
--os-window-radius: 16px; |
| 252 |
/* |
| 253 |
* Shadows stay black and go deeper than they were: on a Void desk |
| 254 |
* a soft grey shadow is invisible, and depth is the only thing |
| 255 |
* separating a window from the sky behind it. |
| 256 |
*/ |
| 257 |
--os-window-shadow: 0 8px 32px rgba(0, 0, 0, 0.5), 0 2px 8px rgba(0, 0, 0, 0.3); |
| 258 |
--os-window-shadow-focused: 0 12px 48px rgba(0, 0, 0, 0.6), 0 4px 12px rgba(0, 0, 0, 0.35); |
| 259 |
/* |
| 260 |
* Fill of the surface a window's content is revealed from once it |
| 261 |
* finishes loading (OS Settings → Effects → "Window reveal"). |
| 262 |
* |
| 263 |
* Obsidian, so a window uncovers from its own colour rather than |
| 264 |
* flashing white on a dark desk. The surface has to be opaque or |
| 265 |
* there is nothing to reveal FROM — the content would simply be |
| 266 |
* visible the whole time and the clip animation would paint |
| 267 |
* nothing. `transparent` is a legitimate value meaning "no |
| 268 |
* covering surface"; the shell then skips the layer rather than |
| 269 |
* animating something invisible. |
| 270 |
* |
| 271 |
* A reveal may override this for itself when the paint IS the |
| 272 |
* reveal; `obturator` (Camera shutter) is the one built-in that |
| 273 |
* does, because near-black blades are what make it a shutter. |
| 274 |
*/ |
| 275 |
--os-window-reveal-surface: #1a1721; |
| 276 |
/* |
| 277 |
* Fill of the reveal's leading edge — the band that travels with |
| 278 |
* the clip boundary and draws each reveal's shape (six lines on |
| 279 |
* Blinds, an opening ring on Iris, a rotating spoke on Radar). |
| 280 |
* |
| 281 |
* `transparent` by default: the reveal reads as the page arriving, |
| 282 |
* and a hard graphic edge on top of that is a deliberate look |
| 283 |
* rather than the neutral one. A theme (or any stylesheet) opts in |
| 284 |
* by giving this a colour — no JS and no per-reveal configuration |
| 285 |
* needed, because the band follows whatever shape the active |
| 286 |
* reveal has. While it computes to fully transparent the shell |
| 287 |
* skips the layer altogether, so the default costs nothing. |
| 288 |
*/ |
| 289 |
--os-window-reveal-edge: transparent; |
| 290 |
|
| 291 |
/* |
| 292 |
* ---- Title bar --------------------------------------------- |
| 293 |
* |
| 294 |
* Obsidian when focused, Void when not: the focused window's |
| 295 |
* chrome sits one step up the Shade ramp while its unfocused |
| 296 |
* neighbours sink toward the desk they are lying on. That is the |
| 297 |
* entire focus signal, and it costs no colour — which matters, |
| 298 |
* because the accent is spoken for. |
| 299 |
* |
| 300 |
* The pair used to be Astro-over-Obsidian, a step higher. It came |
| 301 |
* down so a focused window's title bar and its tab strip are the |
| 302 |
* SAME Obsidian, and the only thing lifting out of that surface is |
| 303 |
* the tab itself. The step is the same size; the whole ramp moved. |
| 304 |
*/ |
| 305 |
--os-titlebar-bg: #0c0b0f; |
| 306 |
--os-titlebar-bg-focused: #1a1721; |
| 307 |
--os-titlebar-color: #99969c; |
| 308 |
--os-titlebar-color-focused: #fffbff; |
| 309 |
--os-titlebar-height: 40px; |
| 310 |
/* Hairline between page chrome and window chrome. */ |
| 311 |
--os-titlebar-divider: rgba(255, 251, 255, 0.12); |
| 312 |
--os-titlebar-divider-unfocused: rgba(255, 251, 255, 0.06); |
| 313 |
|
| 314 |
/* |
| 315 |
* The status ring — leading mark of the title bar, where the app |
| 316 |
* icon used to be. Four states: the resting ring is Starlight, |
| 317 |
* work and success are both Pulse, failure is the danger colour. |
| 318 |
* |
| 319 |
* Pulse twice over is not an oversight. In flight and landed |
| 320 |
* differ in FILL — an open ring breathing, then a solid disc with |
| 321 |
* a check — and failure differs from both in fill AND glyph AND |
| 322 |
* hue. Shape carries the distinction that colour alone cannot for |
| 323 |
* a user who can't separate the two hues, and the accent stays the |
| 324 |
* shell's own voice for "this is your station working". |
| 325 |
* |
| 326 |
* Failure resolves through `--os-ui-danger` and is the one value |
| 327 |
* here that must not be quietened: a failure that whispers is a |
| 328 |
* failure the user misses. |
| 329 |
* |
| 330 |
* The resting ring is one value in both title-bar states, not two: |
| 331 |
* the ring reports a phase, and dimming it on an unfocused window |
| 332 |
* would make `idle` say something different depending on which |
| 333 |
* window you last clicked. |
| 334 |
*/ |
| 335 |
--os-titlebar-activity-idle-color: #fffbff; |
| 336 |
--os-titlebar-activity-color: var(--os-ui-accent, #2271b1); |
| 337 |
--os-titlebar-activity-saved-color: var(--os-ui-accent, #2271b1); |
| 338 |
--os-titlebar-activity-failed-color: var(--os-ui-danger, #d63638); |
| 339 |
--os-titlebar-activity-size: 16px; |
| 340 |
|
| 341 |
/* |
| 342 |
* Title-bar control glyphs — minimise / maximise / close, the ⋯ |
| 343 |
* menu trigger, and the screen-meta cluster — in each of the two |
| 344 |
* title-bar states. |
| 345 |
* |
| 346 |
* Both halves are named explicitly. The unfocused half would |
| 347 |
* otherwise derive itself from `--os-titlebar-color` by |
| 348 |
* a `color-mix()` that only runs while a desktop theme is active, |
| 349 |
* and the focused half cannot derive at all: its glyphs sit on |
| 350 |
* `-bg-focused`, and CSS has no contrast-safe function of a |
| 351 |
* background colour. |
| 352 |
* |
| 353 |
* Close-button red is deliberately not in either set — it is |
| 354 |
* semantic signal, not chrome, and both states resolve it through |
| 355 |
* `--os-ui-danger`. |
| 356 |
*/ |
| 357 |
--os-titlebar-btn-color: rgba(255, 251, 255, 0.55); |
| 358 |
--os-titlebar-btn-color-hover: #fffbff; |
| 359 |
--os-titlebar-btn-bg-hover: rgba(255, 251, 255, 0.1); |
| 360 |
--os-titlebar-btn-bg-active: rgba(255, 251, 255, 0.16); |
| 361 |
--os-titlebar-btn-focused-color: rgba(255, 251, 255, 0.72); |
| 362 |
--os-titlebar-btn-focused-color-hover: #fffbff; |
| 363 |
--os-titlebar-btn-focused-bg-hover: rgba(255, 251, 255, 0.14); |
| 364 |
--os-titlebar-btn-focused-bg-active: rgba(255, 251, 255, 0.2); |
| 365 |
--os-titlebar-btn-focused-outline: #f252fc; |
| 366 |
|
| 367 |
/* |
| 368 |
* The control cluster and each button face stay TRANSPARENT, so a |
| 369 |
* themed title-bar texture runs edge to edge underneath them and |
| 370 |
* the glyphs float on the artwork. A plate behind the controls is |
| 371 |
* a choice a theme makes, not a default the framework imposes. |
| 372 |
* The knobs for building one: |
| 373 |
* |
| 374 |
* Cluster --os-titlebar-controls-bg |
| 375 |
* --os-titlebar-controls-image (+ -repeat, |
| 376 |
* -size, -position) |
| 377 |
* --os-titlebar-controls-radius |
| 378 |
* --os-titlebar-controls-padding (inline) |
| 379 |
* --os-titlebar-controls-gap |
| 380 |
* Screen-meta cluster |
| 381 |
* --os-titlebar-meta-bg / -image / -radius |
| 382 |
* (radius falls through to the controls radius) |
| 383 |
* Each face --os-ui-btn-bg / --os-ui-btn-bg-image / --os-ui-btn-radius |
| 384 |
*/ |
| 385 |
|
| 386 |
/* |
| 387 |
* Admin accent. Pulse, the brand's identity colour, and the value |
| 388 |
* behind the `pulse` swatch that OS Settings → Appearance ships as |
| 389 |
* its default (`includes/accents.php`). The accent picker writes |
| 390 |
* the user's choice into this same property as an inline style, so |
| 391 |
* this is the pre-JS value and the floor under every scheme block |
| 392 |
* below. |
| 393 |
*/ |
| 394 |
--wp-admin-theme-color: #f252fc; |
| 395 |
|
| 396 |
/* Resize handle — larger hit area than visual glyph; corners |
| 397 |
are transparent until hover so they don't compete with the |
| 398 |
window's own drop shadow. */ |
| 399 |
--os-resize-size: 20px; |
| 400 |
--os-resize-color: rgba(255, 251, 255, 0.18); |
| 401 |
|
| 402 |
/* |
| 403 |
* ---- The `--os-ui-*` UI palette ------------------------------ |
| 404 |
* |
| 405 |
* The single vocabulary for every surface, text tone, border, and |
| 406 |
* status colour inside window BODIES — the `<os-*>` component kit |
| 407 |
* AND the feature stylesheets both read these. Setting one value |
| 408 |
* retints everything that uses it, which is what makes a |
| 409 |
* whole-OS repaint eleven declarations rather than a thousand. |
| 410 |
* |
| 411 |
* It reaches further than window bodies: the shell's own |
| 412 |
* body-mounted overlays — toasts, confirm dialogs, context menus, |
| 413 |
* and the command palette — read it too. |
| 414 |
* |
| 415 |
* Roughly 190 component-local tokens (`--os-ui-card-bg`, |
| 416 |
* `--os-ui-table-header-bg`, …) fall through to these, e.g. |
| 417 |
* |
| 418 |
* background: var( --os-ui-card-bg, var( --os-ui-surface, #fff ) ); |
| 419 |
* |
| 420 |
* so the ones named further down are only those whose own literal |
| 421 |
* does NOT chain through the palette and would otherwise stay a |
| 422 |
* light-mode value on a dark station. |
| 423 |
*/ |
| 424 |
|
| 425 |
/* Surfaces — Obsidian on Void, one step up the ramp for elevated. */ |
| 426 |
--os-ui-surface: #1a1721; |
| 427 |
--os-ui-surface-elevated: #33303a; |
| 428 |
--os-ui-surface-sunken: #0c0b0f; |
| 429 |
--os-ui-surface-raised: rgba(255, 251, 255, 0.06); |
| 430 |
--os-ui-surface-subtle: rgba(255, 251, 255, 0.03); |
| 431 |
--os-ui-bg: #1a1721; |
| 432 |
--os-ui-bg-subtle: rgba(255, 251, 255, 0.03); |
| 433 |
|
| 434 |
/* |
| 435 |
* Fields — the surface an input paints, for markup in the LIGHT |
| 436 |
* DOM. |
| 437 |
* |
| 438 |
* The kit's own controls don't need these: `<os-text-field>` and |
| 439 |
* friends resolve `--os-window-bg` inside their shadow roots, |
| 440 |
* which the window chrome sets. A plugin writing a plain |
| 441 |
* `<input>` into a native window's body has neither, and the |
| 442 |
* palette had no general answer — no `surface` variant means |
| 443 |
* "input". What it had was `--os-ui-modal-field-bg`, which is a |
| 444 |
* MODAL token: right value, wrong scope, and the sort of thing a |
| 445 |
* plugin author finds by grepping for a colour that looks close. |
| 446 |
* |
| 447 |
* Consumers keep the pre-brand WordPress-admin literals as their |
| 448 |
* fallbacks — `#fff`, `#8c8f94`, `#2c3338` — so an unstyled page |
| 449 |
* lands on the classic admin's own field, not on nothing: |
| 450 |
* |
| 451 |
* background: var( --os-ui-field-bg, #fff ); |
| 452 |
* border: 1px solid var( --os-ui-field-border, #8c8f94 ); |
| 453 |
* color: var( --os-ui-field-fg, #2c3338 ); |
| 454 |
*/ |
| 455 |
--os-ui-field-bg: #33303a; |
| 456 |
--os-ui-field-border: #4d4a52; |
| 457 |
--os-ui-field-fg: #fffbff; |
| 458 |
|
| 459 |
/* |
| 460 |
* Field sizing. The kit's own `<os-text-field>` and `<os-textarea>` |
| 461 |
* (and every kit control that hosts a typing input) read these for |
| 462 |
* the control's type size and corner. The phone layer raises the |
| 463 |
* size to 16px — below that, iOS zooms the whole page into a |
| 464 |
* focused control and never zooms back — and rounds its search; |
| 465 |
* a theme may do the same anywhere. |
| 466 |
*/ |
| 467 |
--os-ui-field-font-size: 13px; |
| 468 |
--os-ui-field-font-size-compact: 12px; |
| 469 |
--os-ui-field-radius: 6px; |
| 470 |
|
| 471 |
/* Text — Starlight down through the Shade ramp. */ |
| 472 |
--os-ui-fg: #fffbff; |
| 473 |
--os-ui-fg-muted: #b3afb5; |
| 474 |
--os-ui-fg-faint: #66636b; |
| 475 |
--os-ui-text-muted: rgba(255, 251, 255, 0.6); |
| 476 |
/* |
| 477 |
* Text on a filled surface — and the name undersells it. Around |
| 478 |
* forty rules read this token, and only about half of them sit on |
| 479 |
* the accent: the rest are white-on-dark chips that never had a |
| 480 |
* name of their own — the toast, the drag hint, the widget picker, |
| 481 |
* the file-tile lock, the overview labels, every scrim-backed |
| 482 |
* caption in OS Settings. |
| 483 |
* |
| 484 |
* So it is Starlight. Void reads better ON Pulse (5.9:1 against |
| 485 |
* 2.9:1) and was the first choice here, but it turned all of those |
| 486 |
* chips into black text on a near-black wash. One token cannot be |
| 487 |
* both, and the dark-chip half is both larger and the half that |
| 488 |
* fails catastrophically rather than merely weakly. |
| 489 |
* |
| 490 |
* The surfaces that really are a bright fill — ribbons and step |
| 491 |
* chips — name their own dark text below, which is the escape |
| 492 |
* hatch this token leaves open. |
| 493 |
*/ |
| 494 |
--os-ui-fg-on-accent: #fffbff; |
| 495 |
|
| 496 |
/* Lines. */ |
| 497 |
--os-ui-border: #33303a; |
| 498 |
--os-ui-border-strong: #4d4a52; |
| 499 |
|
| 500 |
/* Interaction — light washes, since the surface underneath is dark. */ |
| 501 |
--os-ui-hover: rgba(255, 251, 255, 0.06); |
| 502 |
--os-ui-scrim: rgba(12, 11, 15, 0.72); |
| 503 |
|
| 504 |
/* |
| 505 |
* ---- Text selection ------------------------------------------ |
| 506 |
* |
| 507 |
* Lagoon, the brand's violet-blue, at 60%. It is the one primary |
| 508 |
* colour in the guidelines the shell had no job for, and this is |
| 509 |
* the right job: violet-blue is what every OS has trained people |
| 510 |
* to read as "selected", so it needs no learning. |
| 511 |
* |
| 512 |
* The alpha is where the accessibility is, and it is squeezed from |
| 513 |
* both ends. A selection has to satisfy two constraints at once: |
| 514 |
* |
| 515 |
* 1. the selected TEXT stays readable on it — Starlight over |
| 516 |
* Lagoon@60% is 5.1:1 on Obsidian, 5.5:1 on Void; and |
| 517 |
* 2. the highlight is distinguishable from the unselected |
| 518 |
* background — 3.4:1 and 3.5:1 respectively. |
| 519 |
* |
| 520 |
* Raising the alpha helps (2) and hurts (1); lowering it does the |
| 521 |
* reverse. 60% is the middle of the band where both clear their |
| 522 |
* bar on both surfaces. An accent wash cannot do this at all: the |
| 523 |
* Pulse family only separates from the background above 75%, by |
| 524 |
* which point it is a fill rather than a highlight. |
| 525 |
* |
| 526 |
* The text colour is Starlight — the colour body text already is. |
| 527 |
* A selection that also RECOLOURS the text destroys every |
| 528 |
* distinction the text was carrying: syntax highlighting, a red |
| 529 |
* error, a muted timestamp. Highlighting is not restyling. |
| 530 |
*/ |
| 531 |
--os-ui-selection-bg: rgba(159, 152, 255, 0.6); |
| 532 |
--os-ui-selection-fg: #fffbff; |
| 533 |
|
| 534 |
/* Accent — the identity moment. */ |
| 535 |
--os-ui-accent: #f252fc; |
| 536 |
--os-ui-accent-strong: #ec9bff; |
| 537 |
--os-ui-accent-soft: color-mix(in srgb, var(--os-ui-accent-dim) 14%, transparent); |
| 538 |
/* |
| 539 |
* Pulse, one step back — and the single knob for how loud the |
| 540 |
* station is. |
| 541 |
* |
| 542 |
* Pulse is not a contrast problem: #f252fc carries 6.2:1 against |
| 543 |
* Obsidian, better than most accents in a dark UI manage. What it |
| 544 |
* is, is SATURATED — HSL 296, 97, 65 — and the places that hurt |
| 545 |
* are the ones where it is spread rather than stated: a bloom |
| 546 |
* behind a focused control, a 18% wash under a selected row, a |
| 547 |
* fill wider than a chip. Ten of those on one panel and the whole |
| 548 |
* surface hums. |
| 549 |
* |
| 550 |
* So the fix is not to move Pulse. It is to spend it where it is |
| 551 |
* a statement and to spend THIS where it is atmosphere: the same |
| 552 |
* hue with saturation and lightness pulled down together (S 77, |
| 553 |
* L 53), which is what keeps it recognisably Pulse rather than a |
| 554 |
* different purple. 4.6:1 on Obsidian, and Starlight over it goes |
| 555 |
* from 2.8:1 to 3.8:1 — so the wash also stopped eating text. |
| 556 |
* |
| 557 |
* Everything ambient below resolves through it: the glows, the |
| 558 |
* soft wash, the focus bloom. Turning the station up or down is |
| 559 |
* one edit here. |
| 560 |
* |
| 561 |
* `--os-ui-accent` itself stays #f252fc. That one is the brand's, |
| 562 |
* not ours — it is what the guidelines name and what |
| 563 |
* `brand-palette.test.ts` pins, and moving it is a brand decision |
| 564 |
* rather than a UI one. |
| 565 |
*/ |
| 566 |
--os-ui-accent-dim: #d92ee3; |
| 567 |
|
| 568 |
/* |
| 569 |
* ---- The meshes --------------------------------------------- |
| 570 |
* |
| 571 |
* The brand ships five mesh gradients as SVG artwork. These are |
| 572 |
* those same meshes transcribed into CSS: the base linear plus |
| 573 |
* every radial glow, at the offsets, radii, colours and alphas |
| 574 |
* the vector files declare, converted from the 1440×960 artboard |
| 575 |
* into percentages so they scale to any box. |
| 576 |
* |
| 577 |
* Transcribed rather than referenced on purpose. A `url()` to an |
| 578 |
* SVG cannot be animated, cannot be tinted, costs a request, and |
| 579 |
* cannot resize its glows independently of the box — a mesh |
| 580 |
* painted on a 40 px switch track would be one flat corner of the |
| 581 |
* artwork. As gradient stacks they rasterise at whatever size the |
| 582 |
* control happens to be, and `background-position` can slide them, |
| 583 |
* which is the entire holographic effect: a foil that shifts as |
| 584 |
* you tilt it. |
| 585 |
* |
| 586 |
* Layer order is inverted from the SVG. In SVG the last `<rect>` |
| 587 |
* paints on top; in a CSS `background-image` list the FIRST layer |
| 588 |
* is on top. So each mesh below reads bottom-glow-first and ends |
| 589 |
* with its base linear. |
| 590 |
* |
| 591 |
* The brand's own rule — "meshes reserved for hero surfaces" — is |
| 592 |
* why none of these is a surface colour. They are what the shell |
| 593 |
* paints at an identity moment: a switch that is on, the primary |
| 594 |
* action in a dialog, the filled part of a progress bar. See the |
| 595 |
* `--os-ui-holo-*` block below for the tokens components actually |
| 596 |
* read. |
| 597 |
*/ |
| 598 |
|
| 599 |
/* |
| 600 |
* Holomesh. Lavender base under eight glows — white, cyan, pink, |
| 601 |
* warm, mint, white, pink, blue. The default holographic fill. |
| 602 |
*/ |
| 603 |
--os-mesh-holo: |
| 604 |
radial-gradient(ellipse 21.7% 39.6% at 96.5% 13.5%, rgba(159, 214, 255, 0.6) 0%, rgba(159, 214, 255, 0) 100%), |
| 605 |
radial-gradient(ellipse 26.3% 57.2% at 83.3% 56.2%, rgba(243, 181, 236, 0.75) 0%, rgba(243, 181, 236, 0) 100%), |
| 606 |
radial-gradient(ellipse 18.2% 47.3% at 73.6% 64.5%, rgba(255, 253, 255, 0.7) 0%, rgba(255, 253, 255, 0) 100%), |
| 607 |
radial-gradient(ellipse 18.4% 34.1% at 29.8% 83.4%, rgba(147, 240, 198, 0.8) 0%, rgba(147, 240, 198, 0) 100%), |
| 608 |
radial-gradient(ellipse 17.4% 35.7% at 23% 67.7%, rgba(248, 242, 182, 0.85) 0%, rgba(248, 242, 182, 0) 100%), |
| 609 |
radial-gradient(ellipse 23.3% 45.9% at 45.2% 45.8%, rgba(245, 159, 232, 1) 0%, rgba(245, 168, 234, 0.55) 55%, rgba(245, 168, 234, 0) 100%), |
| 610 |
radial-gradient(ellipse 29.9% 53.6% at 53.5% 7.3%, rgba(125, 239, 245, 0.9) 0%, rgba(142, 233, 247, 0.45) 60%, rgba(142, 233, 247, 0) 100%), |
| 611 |
radial-gradient(ellipse 26.9% 70.7% at 29.8% 44.8%, rgba(255, 253, 255, 0.95) 0%, rgba(255, 253, 255, 0.5) 55%, rgba(255, 253, 255, 0) 100%), |
| 612 |
linear-gradient(124deg, #afa2e8 0%, #b7abea 55%, #c3b8ef 100%); |
| 613 |
|
| 614 |
/* |
| 615 |
* Pulsemesh. The loud one — a blue-to-violet base torn open by |
| 616 |
* magenta. Reserved for the moments Holomesh would undersell. |
| 617 |
*/ |
| 618 |
--os-mesh-pulse: |
| 619 |
radial-gradient(ellipse 39.1% 48.6% at 92% 94.5%, rgba(255, 253, 255, 0.95) 0%, rgba(255, 240, 252, 0.55) 50%, rgba(255, 240, 252, 0) 100%), |
| 620 |
radial-gradient(ellipse 33.3% 50% at 61.1% 62.5%, rgba(251, 134, 236, 0.85) 0%, rgba(251, 134, 236, 0) 100%), |
| 621 |
radial-gradient(ellipse 36.1% 54.2% at 10.4% 39.6%, rgba(250, 61, 248, 1) 0%, rgba(250, 61, 248, 0) 100%), |
| 622 |
radial-gradient(ellipse 87.3% 104.8% at 10.6% 100%, rgba(240, 75, 245, 1) 0%, rgba(240, 75, 245, 0.75) 43%, rgba(240, 75, 245, 0) 100%), |
| 623 |
radial-gradient(ellipse 36.1% 45.8% at 92.4% 12.5%, rgba(125, 239, 245, 0.95) 0%, rgba(125, 239, 245, 0) 100%), |
| 624 |
radial-gradient(ellipse 43.1% 54.2% at 81.3% 34.4%, rgba(108, 143, 245, 0.6) 0%, rgba(108, 143, 245, 0) 100%), |
| 625 |
linear-gradient(236deg, #8d9bf3 0%, #c878f0 100%); |
| 626 |
|
| 627 |
/* Auromesh. Lavender through mint into cyan — the calm mesh. */ |
| 628 |
--os-mesh-auro: linear-gradient(80deg, #d1c6f8 9.5%, #cefada 50%, #b8ffff 90.5%); |
| 629 |
|
| 630 |
/* Starmesh. A Starlight glow falling away into Cloud. */ |
| 631 |
--os-mesh-star: |
| 632 |
radial-gradient(ellipse 72.7% 72.7% at 50% 12.5%, #fffbff 0%, #fffbff 67.8%, #ccc8ce 100%); |
| 633 |
|
| 634 |
/* Miomesh. The mascot's own sweep. Mio's, and used sparingly. */ |
| 635 |
--os-mesh-mio: linear-gradient(90deg, #f252fc 7%, #aa67ff 48.3%, #a580ff 70.7%, #4b3eff 93%); |
| 636 |
|
| 637 |
/* |
| 638 |
* ---- Holographic controls ----------------------------------- |
| 639 |
* |
| 640 |
* What a control reads when it wants to be holographic. Every |
| 641 |
* `<os-*>` resolves these through a private `--_holo-*` alias (see |
| 642 |
* `src/ui/holo.ts`), so a desktop theme can re-point any of them |
| 643 |
* and every control in the kit changes together. |
| 644 |
* |
| 645 |
* The holographic state is a MOMENT, not a skin. A control paints |
| 646 |
* `--os-ui-holo-fill` when it is on, selected, primary or filled — |
| 647 |
* the one instant it is speaking for the brand — and wears |
| 648 |
* ordinary Obsidian the rest of the time. That is the difference |
| 649 |
* between a station and a novelty; a panel where every control is |
| 650 |
* iridescent has no identity moments left to spend. |
| 651 |
*/ |
| 652 |
|
| 653 |
/* The fill itself. Holomesh, so the mesh is the default look. */ |
| 654 |
--os-ui-holo-fill: var(--os-mesh-holo); |
| 655 |
/* |
| 656 |
* A hero FIELD, as distinct from a hero control. |
| 657 |
* |
| 658 |
* `--os-ui-holo-fill` is sized for a surface a control wears — a |
| 659 |
* button, a chip, a progress bar. Stretch that same value across |
| 660 |
* a few hundred square pixels of panel and a theme's answer stops |
| 661 |
* working: Legacy's `#f0f6fc -> #f6f7f7` reads as "on" on a 40px |
| 662 |
* chip and as nothing at all on a rail, where it lands within a |
| 663 |
* few units of the surface behind it. |
| 664 |
* |
| 665 |
* So a large decorative field reads THIS instead, and a theme |
| 666 |
* gets to answer the two cases separately — how a control looks |
| 667 |
* when it is on, and how much of itself the station shows in the |
| 668 |
* background. Legacy sets a flat pre-brand wash here while |
| 669 |
* leaving its control fill alone. |
| 670 |
* |
| 671 |
* The default is an aurora, and it is built differently from the |
| 672 |
* five meshes on purpose. Those are OPAQUE light surfaces — the |
| 673 |
* darkest stop in Holomesh still sits above 60% luminance — which |
| 674 |
* is right for a control that has to read as lit against whatever |
| 675 |
* is behind it. Spread one across a rail and the only way to calm |
| 676 |
* it down is `opacity`, which drags every hue toward the surface |
| 677 |
* underneath: on Void that is grey, and the mesh dies as a |
| 678 |
* grey-mauve smear. |
| 679 |
* |
| 680 |
* So the alpha lives in the COLOUR STOPS here, over transparent. |
| 681 |
* The desk shows through instead of being covered, the hues keep |
| 682 |
* their chroma at any strength, and the field stays dark the way |
| 683 |
* an aurora is dark — light added to a night sky, not a pale |
| 684 |
* sheet laid over one. Hues are the brand's: violet and Nebula |
| 685 |
* through the upper curtains, Sirius cyan and Holomesh's mint |
| 686 |
* below, one wide Pulse bloom tying them together. |
| 687 |
*/ |
| 688 |
--os-ui-hero-mesh: |
| 689 |
radial-gradient(ellipse 62% 38% at 34% 20%, rgba(170, 103, 255, 0.58) 0%, rgba(170, 103, 255, 0) 74%), |
| 690 |
radial-gradient(ellipse 54% 33% at 58% 36%, rgba(236, 155, 255, 0.45) 0%, rgba(236, 155, 255, 0) 76%), |
| 691 |
radial-gradient(ellipse 68% 30% at 26% 50%, rgba(125, 239, 245, 0.32) 0%, rgba(125, 239, 245, 0) 74%), |
| 692 |
radial-gradient(ellipse 58% 28% at 46% 66%, rgba(147, 240, 198, 0.26) 0%, rgba(147, 240, 198, 0) 76%), |
| 693 |
radial-gradient(ellipse 96% 62% at 40% 42%, rgba(242, 82, 252, 0.18) 0%, rgba(242, 82, 252, 0) 82%); |
| 694 |
/* |
| 695 |
* Glyphs and text ON that fill. Void, not Starlight — every mesh |
| 696 |
* in the brand is a LIGHT surface (its darkest stop, Holomesh's |
| 697 |
* #afa2e8, still sits at 62% luminance), so Starlight on it is a |
| 698 |
* white-on-lilac 1.4:1 that looks fine in a mock and is unreadable |
| 699 |
* on a screen. Void carries at 8.6:1 against the same stop. |
| 700 |
*/ |
| 701 |
--os-ui-holo-ink: #0c0b0f; |
| 702 |
/* |
| 703 |
* The hover film. A control that is NOT in its holographic state |
| 704 |
* still hints at one under the pointer: a low-alpha sweep of the |
| 705 |
* mesh's own hues, laid over whatever the surface already is. |
| 706 |
* |
| 707 |
* Alphas are deliberately in the 6–12% range. This lands on |
| 708 |
* Obsidian, where anything stronger stops reading as a sheen and |
| 709 |
* starts reading as a second, wrongly-coloured surface. |
| 710 |
*/ |
| 711 |
--os-ui-holo-sheen: linear-gradient( |
| 712 |
124deg, |
| 713 |
rgba(159, 214, 255, 0.1) 0%, |
| 714 |
rgba(236, 155, 255, 0.12) 34%, |
| 715 |
rgba(242, 82, 252, 0.1) 58%, |
| 716 |
rgba(147, 240, 198, 0.09) 100% |
| 717 |
); |
| 718 |
/* |
| 719 |
* The iridescent hairline. Painted as a gradient on a padding-box |
| 720 |
* mask rather than a `border-color`, because a border cannot hold |
| 721 |
* a gradient and `border-image` loses the corner radius. |
| 722 |
*/ |
| 723 |
--os-ui-holo-edge: linear-gradient( |
| 724 |
124deg, |
| 725 |
rgba(154, 242, 255, 0.7) 0%, |
| 726 |
rgba(236, 155, 255, 0.85) 38%, |
| 727 |
rgba(242, 82, 252, 0.7) 62%, |
| 728 |
rgba(159, 152, 255, 0.6) 100% |
| 729 |
); |
| 730 |
/* Resting edge — the same hairline, quieted, for an idle control. */ |
| 731 |
--os-ui-holo-edge-quiet: linear-gradient( |
| 732 |
124deg, |
| 733 |
rgba(154, 242, 255, 0.22) 0%, |
| 734 |
rgba(236, 155, 255, 0.28) 38%, |
| 735 |
rgba(242, 82, 252, 0.22) 62%, |
| 736 |
rgba(159, 152, 255, 0.2) 100% |
| 737 |
); |
| 738 |
/* |
| 739 |
* The bloom around a holographic surface. Pulse, because on a Void |
| 740 |
* desk the glow is what separates "lit" from "light-coloured". |
| 741 |
*/ |
| 742 |
--os-ui-holo-glow: 0 0 0 1px color-mix(in srgb, var(--os-ui-accent-dim) 20%, transparent), |
| 743 |
0 2px 10px color-mix(in srgb, var(--os-ui-accent-dim) 15%, transparent); |
| 744 |
--os-ui-holo-glow-strong: 0 0 0 1px color-mix(in srgb, var(--os-ui-accent-dim) 30%, transparent), |
| 745 |
0 4px 18px color-mix(in srgb, var(--os-ui-accent-dim) 26%, transparent), |
| 746 |
0 1px 3px rgba(12, 11, 15, 0.6); |
| 747 |
/* |
| 748 |
* The unlit half — switch tracks, empty progress, the unchecked |
| 749 |
* checkbox. |
| 750 |
* |
| 751 |
* This was a sunken Void well, and it was a mistake that measured |
| 752 |
* badly: `rgba(12, 11, 15, 0.55)` composites to #121017 on an |
| 753 |
* Obsidian panel, which is **1.07:1** against that panel. An off |
| 754 |
* switch was, to a very good approximation, not drawn. WCAG 1.4.11 |
| 755 |
* asks for 3:1 on the boundary of a control, and this was not in |
| 756 |
* the same postcode. |
| 757 |
* |
| 758 |
* So the well is LIFTED rather than sunk: a Starlight wash, which |
| 759 |
* also means it tracks whatever surface a theme puts behind it |
| 760 |
* instead of pinning a grey that only works on Obsidian. Every |
| 761 |
* dark OS does the same thing with its switches for the same |
| 762 |
* reason — on a dark UI the visible thing is the lighter one. |
| 763 |
* |
| 764 |
* The fill alone still only reaches ~1.6:1, which is a *look* |
| 765 |
* rather than a boundary. The 3:1 comes from the edge below, and |
| 766 |
* the two together are what make an off switch findable. |
| 767 |
*/ |
| 768 |
--os-ui-holo-track: rgba(255, 251, 255, 0.16); |
| 769 |
/* |
| 770 |
* The unlit half's boundary. Pewter, and not a rounder-looking |
| 771 |
* neighbour, because Pewter is the first step on the Shade ramp |
| 772 |
* that reaches 3.00:1 against Obsidian — Silver manages 2.03 and |
| 773 |
* Astro 1.37. This is the declaration that makes an off control |
| 774 |
* satisfy WCAG 1.4.11. |
| 775 |
*/ |
| 776 |
--os-ui-holo-track-edge: #66636b; |
| 777 |
/* |
| 778 |
* Focus. One ring for the whole kit — Pulse, offset, over a soft |
| 779 |
* halo, so it reads on Obsidian, on a mesh, and on the near-white |
| 780 |
* of a legacy theme alike. |
| 781 |
* |
| 782 |
* Note which layer dims and which does not. The RING is full Pulse |
| 783 |
* and stays there: it is the only thing on screen saying where the |
| 784 |
* keyboard is, and a focus indicator is the last place to trade |
| 785 |
* legibility for calm. Only the bloom behind it comes down, from |
| 786 |
* 45% to 30%, and onto the dim — which is the layer that was |
| 787 |
* making a focused control look like it was on fire. |
| 788 |
*/ |
| 789 |
--os-ui-focus-ring: 0 0 0 2px rgba(12, 11, 15, 0.9), |
| 790 |
0 0 0 4px var(--os-ui-accent, #f252fc), |
| 791 |
0 0 12px 2px color-mix(in srgb, var(--os-ui-accent-dim) 30%, transparent); |
| 792 |
/* |
| 793 |
* …and one for FIELDS, which is a different problem. A text input |
| 794 |
* already has a border to thicken and it sits in a column of other |
| 795 |
* inputs, so the ring above — designed to survive landing on a |
| 796 |
* bright mesh — reads as an alarm on a settings form. This one |
| 797 |
* tightens the field's own edge to Pulse and puts a soft halo |
| 798 |
* outside it: unmistakable, and quiet enough to live in a stack of |
| 799 |
* twelve. |
| 800 |
*/ |
| 801 |
--os-ui-focus-ring-field: 0 0 0 1px var(--os-ui-accent, #f252fc), |
| 802 |
0 0 0 4px color-mix(in srgb, var(--os-ui-accent-dim) 16%, transparent); |
| 803 |
|
| 804 |
/* |
| 805 |
* The selected row of a VERTICAL `<os-tabs>`: the sidebar in |
| 806 |
* OpenStation Preferences, and any native window that lays its |
| 807 |
* pages down the side rather than across the top. |
| 808 |
* |
| 809 |
* Three layers, and the split is the whole point. Colour repeated |
| 810 |
* down nine rows is wallpaper, so the accent is spent as a |
| 811 |
* two-pixel EDGE and the row itself gets only a wash that falls |
| 812 |
* away: it appears where it is cheap to look at and expensive to |
| 813 |
* ignore. |
| 814 |
* |
| 815 |
* `-edge` is the accent the user picked, flat. It used to be |
| 816 |
* Miomesh, and a mesh does hold up at 2px where a radial one |
| 817 |
* would crop to an arbitrary lilac — but the edge is the loudest |
| 818 |
* thing on the page that says "this row", and a row that says it |
| 819 |
* in Pulse while the controls beside it say it in the chosen |
| 820 |
* accent reads as two systems. |
| 821 |
* |
| 822 |
* `-wash` and `-bloom` are AMBIENT accent, so both resolve through |
| 823 |
* `--os-ui-accent-dim` like every other glow in the kit. Turning |
| 824 |
* the station down is still one edit. The Starlight stop in the |
| 825 |
* middle of the wash is what keeps the row from reading as a pink |
| 826 |
* smear: it lifts the surface under the label rather than tinting |
| 827 |
* it, and it is gone by the time the row ends. |
| 828 |
*/ |
| 829 |
--os-ui-tab-edge: linear-gradient( |
| 830 |
var(--os-ui-accent, #f252fc), |
| 831 |
var(--os-ui-accent, #f252fc) |
| 832 |
); |
| 833 |
--os-ui-tab-wash: linear-gradient( |
| 834 |
90deg, |
| 835 |
color-mix(in srgb, var(--os-ui-accent-dim) 16%, transparent) 0%, |
| 836 |
rgba(255, 251, 255, 0.04) 42%, |
| 837 |
transparent 100% |
| 838 |
); |
| 839 |
--os-ui-tab-bloom: linear-gradient( |
| 840 |
90deg, |
| 841 |
color-mix(in srgb, var(--os-ui-accent-dim) 26%, transparent), |
| 842 |
transparent |
| 843 |
); |
| 844 |
|
| 845 |
/* |
| 846 |
* ---- Motion -------------------------------------------------- |
| 847 |
* |
| 848 |
* Four durations and three curves, and every animated thing in the |
| 849 |
* kit picks from them. Not for tidiness: a panel where the switch |
| 850 |
* settles in 220ms, the segmented thumb in 300 and the tab |
| 851 |
* underline in 150 does not read as three well-tuned controls, it |
| 852 |
* reads as one surface that cannot keep time. |
| 853 |
* |
| 854 |
* The scale is roughly logarithmic because perceived duration is: |
| 855 |
* 90 and 140 are distinguishable, 220 and 240 are not. |
| 856 |
*/ |
| 857 |
/* A state flip with no travel — a colour, an opacity, a tick. */ |
| 858 |
--os-ui-motion-fast: 140ms; |
| 859 |
/* |
| 860 |
* How long the foil takes to tilt, and the kit's default. One |
| 861 |
* duration for every holographic transition, so a panel full of |
| 862 |
* controls moves as one surface rather than as thirty independent |
| 863 |
* ones. |
| 864 |
*/ |
| 865 |
--os-ui-holo-transition: 220ms; |
| 866 |
/* Something crossing a distance: a thumb, a drawer, a card. */ |
| 867 |
--os-ui-motion-slow: 340ms; |
| 868 |
/* An ambient loop — a shimmer, a drift. Long enough to ignore. */ |
| 869 |
--os-ui-motion-ambient: 12s; |
| 870 |
|
| 871 |
/* |
| 872 |
* The curves. `spring` overshoots ~9% and settles; it is what makes |
| 873 |
* a knob feel thrown rather than moved, and it is wrong for |
| 874 |
* anything that changes size (an overshooting width reads as a |
| 875 |
* glitch, not as weight). |
| 876 |
*/ |
| 877 |
--os-ui-ease-spring: cubic-bezier(0.32, 1.5, 0.55, 1); |
| 878 |
/* Decelerating. The default for anything arriving. */ |
| 879 |
--os-ui-ease-out: cubic-bezier(0.22, 0.9, 0.28, 1); |
| 880 |
/* |
| 881 |
* Accelerating — the mirror of `out`, and the default for anything |
| 882 |
* LEAVING. A surface that eases out on the way in and eases in on |
| 883 |
* the way out is the difference between "dismissed" and "undone": |
| 884 |
* decelerating into nothing reads as the thing hesitating, which |
| 885 |
* is the wrong note when the user has already moved on. |
| 886 |
*/ |
| 887 |
--os-ui-ease-in: cubic-bezier(0.4, 0, 1, 1); |
| 888 |
/* Symmetric, for a loop that has to come back where it started. */ |
| 889 |
--os-ui-ease-loop: cubic-bezier(0.45, 0, 0.55, 1); |
| 890 |
|
| 891 |
/* |
| 892 |
* Status. Derived, not quoted — see the header note. Info takes |
| 893 |
* Sirius and success takes Holomesh's mint because the brand |
| 894 |
* already has a colour that means those things; danger and warning |
| 895 |
* are the shell's own hues lifted until they carry on Obsidian. |
| 896 |
*/ |
| 897 |
--os-ui-danger: #ff5a5a; |
| 898 |
--os-ui-danger-hover: #ff8a8a; |
| 899 |
--os-ui-success-fg: #93f0c6; |
| 900 |
--os-ui-warning-fg: #f8f2b6; |
| 901 |
--os-ui-warning: #f8f2b6; |
| 902 |
--os-ui-warning-bg: rgba(248, 242, 182, 0.1); |
| 903 |
--os-ui-warning-border: rgba(248, 242, 182, 0.24); |
| 904 |
--os-ui-info-fg: #c2f1f1; |
| 905 |
--os-ui-info-bg: rgba(194, 241, 241, 0.1); |
| 906 |
|
| 907 |
/* |
| 908 |
* ---- Component tokens the palette cannot reach -------------- |
| 909 |
* |
| 910 |
* Each of these is read with a literal of its own rather than a |
| 911 |
* `var( --os-ui-<palette> )` chain, so the palette above does not |
| 912 |
* carry to it. Everything else in the kit is left alone and |
| 913 |
* inherits. |
| 914 |
*/ |
| 915 |
|
| 916 |
/* |
| 917 |
* Dialogs, menus and flyouts. |
| 918 |
* |
| 919 |
* The `--os-ui-modal-*` names below are the escape hatch |
| 920 |
* `<os-modal>` needs. Its dialog surface is dark whatever the |
| 921 |
* admin colour scheme says, so it re-points `--os-ui-fg`, |
| 922 |
* `--os-ui-fg-muted`, `--os-ui-border`, `--os-window-bg` and |
| 923 |
* `--os-ui-button-bg-hover` on its own `:host` — and a declaration |
| 924 |
* on the host outranks anything the host inherits, which is how |
| 925 |
* the palette used to stop at the dialog's edge. It reads these |
| 926 |
* instead, so the station owns the dialog again and the literals |
| 927 |
* behind them stay as the no-stylesheet floor. |
| 928 |
* |
| 929 |
* The set has to cover a dark context COMPLETELY, and the four |
| 930 |
* added last are the ones that proved it. A dialog re-pointing |
| 931 |
* only its text colours is fine while the palette around it is |
| 932 |
* dark too — every unre-pointed token happens to agree. Put a |
| 933 |
* LIGHT palette outside it (any theme in the admin's own colours, |
| 934 |
* Legacy included) and the halves come apart: `--os-ui-surface` |
| 935 |
* stays white, so `<os-select>` inside the dialog painted a white |
| 936 |
* trigger and the re-pointed `--os-ui-fg` wrote near-white text |
| 937 |
* onto it. `--os-ui-hover` was a black wash over a dark row. |
| 938 |
* |
| 939 |
* So the rule for anything added here: if a token names a SURFACE |
| 940 |
* or a wash on one, the dialog owns it. Leaving one out is not |
| 941 |
* "inherit the theme", it is "disagree with the other five". |
| 942 |
*/ |
| 943 |
--os-ui-modal-bg: #1a1721; |
| 944 |
--os-ui-modal-text: #fffbff; |
| 945 |
--os-ui-modal-text-muted: #b3afb5; |
| 946 |
--os-ui-modal-border: #4d4a52; |
| 947 |
--os-ui-modal-field-bg: #33303a; |
| 948 |
--os-ui-modal-button-bg-hover: rgba(255, 251, 255, 0.14); |
| 949 |
--os-ui-modal-surface: #1a1721; |
| 950 |
--os-ui-modal-surface-elevated: #33303a; |
| 951 |
--os-ui-modal-border-strong: #4d4a52; |
| 952 |
--os-ui-modal-hover: rgba(255, 251, 255, 0.06); |
| 953 |
--os-ui-confirm-dialog-bg: #1a1721; |
| 954 |
--os-ui-context-menu-bg: #1a1721; |
| 955 |
--os-ui-context-menu-separator-color: rgba(255, 251, 255, 0.1); |
| 956 |
--os-ui-flyout-shadow: 0 16px 48px rgba(0, 0, 0, 0.6); |
| 957 |
--os-ui-card-shadow-hover: 0 4px 16px rgba(0, 0, 0, 0.45); |
| 958 |
--os-ui-ribbon-shadow: 0 2px 4px rgba(0, 0, 0, 0.45); |
| 959 |
|
| 960 |
/* Tables. */ |
| 961 |
--os-ui-table-bg: #1a1721; |
| 962 |
--os-ui-table-header-bg: #33303a; |
| 963 |
--os-ui-table-border: rgba(255, 251, 255, 0.1); |
| 964 |
--os-ui-table-column-border: rgba(255, 251, 255, 0.16); |
| 965 |
--os-ui-table-row-hover: rgba(255, 251, 255, 0.06); |
| 966 |
--os-ui-table-stripe: rgba(255, 251, 255, 0.03); |
| 967 |
--os-ui-table-sticky-edge: 2px solid rgba(255, 251, 255, 0.14); |
| 968 |
|
| 969 |
/* Notices and badges — tinted washes of their own status colour. */ |
| 970 |
--os-ui-notice-error-bg: rgba(255, 90, 90, 0.12); |
| 971 |
--os-ui-notice-error-border: rgba(255, 90, 90, 0.28); |
| 972 |
--os-ui-notice-success-bg: rgba(147, 240, 198, 0.12); |
| 973 |
--os-ui-notice-success-border: rgba(147, 240, 198, 0.28); |
| 974 |
--os-ui-notice-warning-bg: rgba(248, 242, 182, 0.12); |
| 975 |
--os-ui-notice-warning-border: rgba(248, 242, 182, 0.28); |
| 976 |
--os-ui-notice-info-bg: rgba(194, 241, 241, 0.12); |
| 977 |
--os-ui-notice-info-border: rgba(194, 241, 241, 0.28); |
| 978 |
--os-ui-notice-neutral-bg: rgba(255, 251, 255, 0.06); |
| 979 |
--os-ui-notice-neutral-border: rgba(255, 251, 255, 0.14); |
| 980 |
/* |
| 981 |
* A link inside a notice reads Nebula, the same value `--os-link` |
| 982 |
* gives every other shell link — NOT the accent. |
| 983 |
* |
| 984 |
* Undeclared, the base fell through to `--wp-admin-theme-color`, |
| 985 |
* which OpenStation Preferences → Appearance writes inline on `<html>` |
| 986 |
* from the accent picker. That made the one piece of text a notice |
| 987 |
* most needs the user to read take whichever hue they chose for |
| 988 |
* focus rings. An accent is an identity colour; legibility on a dark |
| 989 |
* surface is not something it can promise, so the link stops asking |
| 990 |
* it to. Hover lifts to Starlight, and both ends stay in the palette. |
| 991 |
* |
| 992 |
* These are consumed from a DOCUMENT-tree rule in `desktop.css`, not |
| 993 |
* only from the component's own `::slotted( a )`. See the comment |
| 994 |
* there: a slotted link is a document-tree element, so wp-admin's |
| 995 |
* bare `a` rule outranks anything the shadow root says about it. |
| 996 |
*/ |
| 997 |
--os-ui-notice-link: #ec9bff; |
| 998 |
--os-ui-notice-link-hover: #fffbff; |
| 999 |
--os-ui-badge-danger-bg: rgba(255, 90, 90, 0.16); |
| 1000 |
--os-ui-badge-success-bg: rgba(147, 240, 198, 0.16); |
| 1001 |
--os-ui-badge-warning-bg: rgba(248, 242, 182, 0.16); |
| 1002 |
--os-ui-badge-info-bg: rgba(194, 241, 241, 0.16); |
| 1003 |
--os-ui-badge-neutral-bg: rgba(255, 251, 255, 0.08); |
| 1004 |
|
| 1005 |
/* |
| 1006 |
* Fills that must stay fills. Each of these paints a solid shape — |
| 1007 |
* a ribbon, a chip, a focused input's edge — and each was reading |
| 1008 |
* a token the palette turned into a 10%-alpha wash or into the |
| 1009 |
* body colour itself. A ribbon the same colour as the card behind |
| 1010 |
* it is not a subtle ribbon, it is a missing one. |
| 1011 |
*/ |
| 1012 |
/* |
| 1013 |
* Text on the bright status fills. These are the surfaces the |
| 1014 |
* `--os-ui-fg-on-accent` note points at: a ribbon filled with Pulse, |
| 1015 |
* Sirius or Holomesh mint is a LIGHT surface, and Starlight on it |
| 1016 |
* disappears. |
| 1017 |
*/ |
| 1018 |
--os-ui-ribbon-fg: #0c0b0f; |
| 1019 |
--os-ui-step-chip-fg: #0c0b0f; |
| 1020 |
/* |
| 1021 |
* The step chip is the right size and shape for the mesh: a small |
| 1022 |
* round fill, one per row, already carrying dark text. Its |
| 1023 |
* `--os-ui-step-chip-fg` above is Void, which is what the mesh |
| 1024 |
* needs anyway — the two decisions were made independently and |
| 1025 |
* agree, which is usually the sign a palette is holding together. |
| 1026 |
*/ |
| 1027 |
--os-ui-step-chip-bg: var(--os-mesh-holo); |
| 1028 |
|
| 1029 |
/* |
| 1030 |
* The default ribbon. One per tile, small, angled, and already |
| 1031 |
* paired with Void ink above — which is what a mesh needs anyway. |
| 1032 |
* The status ribbons below keep their flat colours: a ribbon that |
| 1033 |
* says "deprecated" should say it in warning yellow, not in brand. |
| 1034 |
*/ |
| 1035 |
--os-ui-ribbon-bg: var(--os-mesh-holo); |
| 1036 |
|
| 1037 |
--os-ui-ribbon-info: #c2f1f1; |
| 1038 |
--os-ui-ribbon-warning: #f8f2b6; |
| 1039 |
--os-ui-ribbon-neutral: #4d4a52; |
| 1040 |
--os-ui-crumb-bg: #33303a; |
| 1041 |
--os-ui-tag-input-input-border: #f252fc; |
| 1042 |
|
| 1043 |
/* |
| 1044 |
* Pairs that have to stay distinguishable. Hover and pressed, or |
| 1045 |
* base and shimmer, both resolve through `--os-ui-hover` — one wash |
| 1046 |
* for two states reads as a dead control, so the second step of |
| 1047 |
* each pair is named. |
| 1048 |
*/ |
| 1049 |
--os-ui-btn-bg-active: rgba(255, 251, 255, 0.12); |
| 1050 |
/* |
| 1051 |
* `<os-button>` ghost + secondary. Their resting wash and their |
| 1052 |
* hover wash BOTH fall through to `--os-ui-hover` — in two different |
| 1053 |
* rules, with two different literals behind them (6% and 10%), so |
| 1054 |
* declaring the palette collapsed them onto one value and the |
| 1055 |
* buttons stopped reacting to the pointer entirely. Primary is |
| 1056 |
* unaffected: it hovers with `filter: brightness()` over its |
| 1057 |
* accent fill rather than through this token. |
| 1058 |
*/ |
| 1059 |
--os-ui-button-bg-hover: rgba(255, 251, 255, 0.14); |
| 1060 |
--os-ui-key-bg-hover: rgba(255, 251, 255, 0.1); |
| 1061 |
--os-ui-key-bg-pressed: rgba(255, 251, 255, 0.16); |
| 1062 |
--os-ui-table-skeleton-highlight: rgba(255, 251, 255, 0.14); |
| 1063 |
|
| 1064 |
/* Code, logs, progress, ratings, avatars. */ |
| 1065 |
--os-ui-code-border: 1px solid rgba(255, 251, 255, 0.1); |
| 1066 |
--os-ui-log-border: 1px solid rgba(255, 251, 255, 0.08); |
| 1067 |
--os-ui-log-row-border: 1px solid rgba(255, 251, 255, 0.06); |
| 1068 |
--os-ui-progress-track-bg: rgba(255, 251, 255, 0.1); |
| 1069 |
/* |
| 1070 |
* The filled part of a progress bar is the one surface in the kit |
| 1071 |
* that is *already* a hero: bounded, watched, and the only thing |
| 1072 |
* moving on screen. So it takes Holomesh, and the bar stretches |
| 1073 |
* the mesh as it grows — the hue travelling from lavender toward |
| 1074 |
* cyan IS the progress, which a flat accent could only report. |
| 1075 |
* |
| 1076 |
* Retinted here rather than in `<os-progress-bar>` because the |
| 1077 |
* component's own literal has to stay the pre-brand WordPress blue |
| 1078 |
* (it is the no-stylesheet floor, and it is what Legacy collected). |
| 1079 |
* The tone modifiers — success, warning, danger — still declare |
| 1080 |
* flat colours and still win: a failing job should read as red, not |
| 1081 |
* as brand. |
| 1082 |
*/ |
| 1083 |
--os-ui-progress-fill: var(--os-mesh-holo); |
| 1084 |
--os-ui-rating-star: #f8f2b6; |
| 1085 |
--os-ui-rating-fill: linear-gradient(90deg, #f8f2b6 0%, #fffbff 100%); |
| 1086 |
--os-ui-avatar-dot-ring: #1a1721; |
| 1087 |
/* The avatar's hover halo. It was a fixed indigo — a hue no |
| 1088 |
palette in the station names — so it lit itself in a colour |
| 1089 |
nothing around it used. Pulse. */ |
| 1090 |
--os-ui-avatar-halo: #f252fc; |
| 1091 |
/* Search-match highlight inside a label. A WASH, not a fill: the |
| 1092 |
text keeps its own colour, so the wash has to stay light enough |
| 1093 |
for Starlight to carry over it. */ |
| 1094 |
--os-ui-search-highlight-bg: rgba(248, 242, 182, 0.3); |
| 1095 |
/* |
| 1096 |
* The content graph's cluster hue is NOT retinted. Graph node |
| 1097 |
* colours are composed artwork that encodes meaning — the docs list |
| 1098 |
* them under "what stays fixed" — and moving this one to Nebula put |
| 1099 |
* white cluster labels on a pale lilac chip at 1.9:1. It keeps its |
| 1100 |
* own colour, and the label keeps carrying on it. |
| 1101 |
* |
| 1102 |
* The graph's toolbar is chrome, though, and it does follow. The |
| 1103 |
* count pill on an ACTIVE filter chip is a 70%-white fill, and it |
| 1104 |
* was carrying `--os-ui-accent-strong` numerals — Nebula on white, |
| 1105 |
* ~1.7:1. It is one more bright fill naming its own dark text, the |
| 1106 |
* same escape hatch `--os-ui-ribbon-fg` and `--os-ui-step-chip-fg` |
| 1107 |
* take, and for the same reason. |
| 1108 |
*/ |
| 1109 |
--os-ui-cg-chip-count-fg-active: #0c0b0f; |
| 1110 |
|
| 1111 |
/* |
| 1112 |
* ---- The widget card's public token contract ---------------- |
| 1113 |
* |
| 1114 |
* Five names a third-party widget stylesheet is told to read. |
| 1115 |
* The list lives in `src/plugins/starter-widget/styles.css`, |
| 1116 |
* which is the file plugin authors copy — so it is a contract, |
| 1117 |
* not a convenience, and four of the five were documented |
| 1118 |
* without ever being declared. Every consumer fell through to |
| 1119 |
* the light-mode grey in its own `var()` fallback, on a card |
| 1120 |
* whose glass is dark: Post Stats' metadata measured 3.81:1 |
| 1121 |
* where `.os-widgets__title` on the same surface measures 18.4. |
| 1122 |
* |
| 1123 |
* They are mostly literals rather than aliases of the text ramp, |
| 1124 |
* and that is the point. `.os-widgets__card` paints a fixed dark |
| 1125 |
* glass — `--os-ui-color-surface` below IS that colour, and the |
| 1126 |
* card reads it — under every desktop theme, so a name that |
| 1127 |
* flips with the theme is the wrong chain here: Legacy's |
| 1128 |
* `--os-ui-fg-muted` is `#50575e`, which lands at 2.54:1 on the |
| 1129 |
* glass and makes the bug WORSE for anyone wearing it. The two |
| 1130 |
* text names below do chain, but through the two names Legacy |
| 1131 |
* keeps light — the ones describing the same on-dark chrome |
| 1132 |
* this card is. |
| 1133 |
* |
| 1134 |
* A theme that wants to move a widget card declares these names |
| 1135 |
* itself, the way Legacy already declares the accent. |
| 1136 |
*/ |
| 1137 |
--os-ui-color-surface: rgba(20, 20, 22, 0.55); |
| 1138 |
/* What the card's own `color` already resolves to — so a widget |
| 1139 |
asking for "primary text" gets the text it inherited. */ |
| 1140 |
--os-ui-color-text: var(--os-ui-fg-on-accent, #fffbff); |
| 1141 |
/* The shell's muted-on-dark. 9.2:1 on the glass, and Legacy |
| 1142 |
keeps it at `rgba( 255, 255, 255, 0.7 )`. */ |
| 1143 |
--os-ui-color-text-subtle: var(--os-fg-muted, rgba(255, 251, 255, 0.7)); |
| 1144 |
/* A hairline INSIDE the card, so a touch stronger than the |
| 1145 |
card's own 0.08 edge, which is drawn against the wallpaper. |
| 1146 |
Literal because no general on-dark hairline exists: the ones |
| 1147 |
Legacy keeps light are `--os-dock-border` and |
| 1148 |
`--os-cn-border`, and borrowing either is the right value at |
| 1149 |
the wrong scope. It reads quieter than what it replaces — |
| 1150 |
the widgets' own fallback was `#e5e7eb`, a light-theme |
| 1151 |
divider that on dark glass drew the loudest line in the |
| 1152 |
station. 0.12 is what the window and dock edges use. */ |
| 1153 |
--os-ui-color-border: rgba(255, 251, 255, 0.12); |
| 1154 |
/* The one name that has to reach the accent picker. It was a |
| 1155 |
hard `#f252fc`, so a widget told to "use the accent for |
| 1156 |
buttons and links" stayed brand pink after the user chose |
| 1157 |
teal, while every control around it moved. */ |
| 1158 |
--os-ui-color-accent: var(--os-ui-accent, #f252fc); |
| 1159 |
|
| 1160 |
/* |
| 1161 |
* ---- Typography -------------------------------------------- |
| 1162 |
* |
| 1163 |
* Geist for everything human — headlines, UI copy, body text — and |
| 1164 |
* Geist Mono for the instrument voice: labels, metadata, statuses, |
| 1165 |
* code. Both faces are declared above; a stack without them still |
| 1166 |
* reads correctly, which is why every entry ends in a generic |
| 1167 |
* family. |
| 1168 |
* |
| 1169 |
* The chrome / body split is the one real decision here, and it is |
| 1170 |
* the one real desktop environments make. Here both sides run |
| 1171 |
* Geist: the station is one surface, and the title bar is not a |
| 1172 |
* different product from the window under it. |
| 1173 |
* |
| 1174 |
* Note that iframe windows render a real wp-admin document in a |
| 1175 |
* separate browsing context that this stylesheet does not reach — |
| 1176 |
* these tokens style the shell and native windows. |
| 1177 |
*/ |
| 1178 |
--os-font: 'Geist', system-ui, sans-serif; |
| 1179 |
--os-titlebar-font: 'Geist', system-ui, sans-serif; |
| 1180 |
--os-ui-font: 'Geist', system-ui, sans-serif; |
| 1181 |
--os-ui-font-mono: 'Geist Mono', ui-monospace, monospace; |
| 1182 |
|
| 1183 |
/* |
| 1184 |
* ---- Desktop-theme texture family ------------------------- |
| 1185 |
* |
| 1186 |
* These are DELIBERATELY not declared. Every rule that consumes |
| 1187 |
* one reads it as `var( --name, <initial> )`, so an unset variable |
| 1188 |
* resolves to the CSS initial value and costs exactly nothing. |
| 1189 |
* Declaring them with `none` up here would be equivalent but would |
| 1190 |
* imply they are part of the default palette — they are not. They |
| 1191 |
* exist only while an uploaded or code-registered desktop theme is |
| 1192 |
* active, and only the compiled theme stylesheet ever sets them. |
| 1193 |
* |
| 1194 |
* TITLEBAR --os-titlebar-image |
| 1195 |
* --os-titlebar-image-repeat |
| 1196 |
* --os-titlebar-image-size |
| 1197 |
* TITLEBAR_FOCUSED --os-titlebar-image-focused |
| 1198 |
* (falls back to the unfocused image) |
| 1199 |
* WINDOW_FRAME --os-window-border-image-source |
| 1200 |
* --os-window-border-image-slice |
| 1201 |
* --os-window-border-image-width |
| 1202 |
* --os-window-border-image-repeat |
| 1203 |
* WINDOW_CORNER_* --os-window-corner-{ne,nw,se,sw}-image |
| 1204 |
* --os-window-corner-size (shared) |
| 1205 |
* --os-window-corner-inset (shared; |
| 1206 |
* how far inside the rounded corner the |
| 1207 |
* ornament sits. Defaults to the resize |
| 1208 |
* handle's 3px overhang plus a share of |
| 1209 |
* --os-window-radius, because the |
| 1210 |
* window clips its descendants) |
| 1211 |
* WINDOW_FRAME_FOCUSED |
| 1212 |
* --os-window-border-image-focused-* |
| 1213 |
* (same four sub-properties as WINDOW_FRAME) |
| 1214 |
* WINDOW_BODY --os-window-body-image |
| 1215 |
* TABBAR --os-tabs-image |
| 1216 |
* TITLEBAR_CONTROLS --os-titlebar-controls-image |
| 1217 |
* TITLEBAR_BUTTON --os-ui-btn-bg-image |
| 1218 |
* DOCK --os-dock-bg-image |
| 1219 |
* --os-dock-bg-image-repeat |
| 1220 |
* --os-dock-bg-image-size |
| 1221 |
* DOCK_ITEM --os-dock-item-image |
| 1222 |
* DESKTOP --os-desktop-image |
| 1223 |
* --os-desktop-image-repeat |
| 1224 |
* --os-desktop-image-size |
| 1225 |
* ICON_TILE --os-tile-image |
| 1226 |
* WIDGET --os-widget-image |
| 1227 |
* MENU --os-ui-menu-bg-image |
| 1228 |
* DIALOG --os-ui-dialog-bg-image |
| 1229 |
* SCRIM --os-ui-scrim-image |
| 1230 |
* PANEL --os-ui-panel-bg-image |
| 1231 |
* TOAST --os-ui-toast-bg-image |
| 1232 |
* TABLE_HEADER --os-ui-table-header-bg-image |
| 1233 |
* BUTTON --os-ui-button-bg-image |
| 1234 |
* |
| 1235 |
* Every `image` slot also gets `<prop>-repeat` and `<prop>-size` |
| 1236 |
* companions (the corners share one `-size`, and |
| 1237 |
* TITLEBAR_FOCUSED inherits TITLEBAR's). |
| 1238 |
* |
| 1239 |
* Consumers: window-chrome.css (titlebar, frame, body, tab bar), |
| 1240 |
* window-states.css (corners), dock.css, desktop.css (wallpaper, |
| 1241 |
* icons, widgets), and the `<os-*>` component stylesheets under |
| 1242 |
* `src/ui/components/` for the last seven. |
| 1243 |
* Authoring reference: docs/desktop-themes.md. |
| 1244 |
*/ |
| 1245 |
|
| 1246 |
/* |
| 1247 |
* ---- Badges ---------------------------------------------- |
| 1248 |
* |
| 1249 |
* Sizes stay undeclared and DERIVED: every badge sizes itself off |
| 1250 |
* the icon it decorates — the dock badge off |
| 1251 |
* `--os-dock-icon-size`, the wallpaper badges off |
| 1252 |
* `--os-icon-image-size` — so a user who picks a large |
| 1253 |
* dock, or a theme that scales its icons, doesn't end up with a |
| 1254 |
* speck stuck to an oversized tile. |
| 1255 |
* |
| 1256 |
* Dock --os-dock-badge-size (overrides the |
| 1257 |
* whole derivation; font + padding follow it) |
| 1258 |
* --os-dock-badge-font-size / -padding |
| 1259 |
* --os-dock-badge-offset / -bg / -fg |
| 1260 |
* --os-dock-badge-font-weight |
| 1261 |
* Desktop icon --os-icon-badge-size / -font-size |
| 1262 |
* --os-icon-badge-padding / -bg / -fg |
| 1263 |
* Recycle bin --os-recycle-badge-size / -font-size |
| 1264 |
* / -bg / -fg. Falls through to the generic |
| 1265 |
* icon-badge token, so "badges are 22px" reaches |
| 1266 |
* the bin too. |
| 1267 |
* |
| 1268 |
* The count badges wear Pulse, and wear it as a LITERAL gradient: |
| 1269 |
* both stops used to resolve through `--os-ui-danger`, which the |
| 1270 |
* palette moved, flattening the badge to one flat fill and turning |
| 1271 |
* its numerals Void by accident. Naming the stops here keeps it a |
| 1272 |
* gradient on purpose. The bin's neutral badge is deliberately not |
| 1273 |
* part of this: a count of things in the trash is ambient state, |
| 1274 |
* not something asking for you. |
| 1275 |
* |
| 1276 |
* **The numerals are Void, not Starlight, and that is a |
| 1277 |
* requirement rather than a preference.** Starlight on Pulse is |
| 1278 |
* 2.9:1, which fails AA for text this small; Void on Pulse is |
| 1279 |
* 6.8:1. Any future retint of these has to keep the pair legible, |
| 1280 |
* so check the ratio before swapping the ink back to white. |
| 1281 |
*/ |
| 1282 |
--os-dock-badge-bg: linear-gradient(180deg, #f97dff 0%, #f252fc 100%); |
| 1283 |
--os-dock-badge-fg: #0c0b0f; |
| 1284 |
--os-icon-badge-bg: linear-gradient(180deg, #f97dff 0%, #f252fc 100%); |
| 1285 |
--os-icon-badge-fg: #0c0b0f; |
| 1286 |
--os-recycle-badge-bg: rgba(26, 23, 33, 0.85); |
| 1287 |
--os-recycle-badge-fg: rgba(255, 251, 255, 0.96); |
| 1288 |
--os-dock-recycle-badge-bg: rgba(26, 23, 33, 0.85); |
| 1289 |
--os-dock-recycle-badge-fg: rgba(255, 251, 255, 0.92); |
| 1290 |
|
| 1291 |
/* |
| 1292 |
* ---- Tooltips --------------------------------------------- |
| 1293 |
* |
| 1294 |
* Two tokens own every tooltip CHIP in the shell — the dock tile |
| 1295 |
* tooltip and the content-graph satellite tooltip. |
| 1296 |
* |
| 1297 |
* They are worth naming rather than leaving derived. Without them |
| 1298 |
* tooltips borrow their colours from unrelated families — |
| 1299 |
* `--os-ui-scrim` (an overlay BACKDROP) or `--os-ui-surface-elevated` |
| 1300 |
* for the surface, `--os-ui-fg-on-accent` for the text — and those |
| 1301 |
* pairings come apart the moment the palette moves. On this |
| 1302 |
* palette `--os-ui-fg-on-accent` is Void, which would have rendered |
| 1303 |
* near-black text on a near-black chip. |
| 1304 |
* |
| 1305 |
* A chip is deliberately the SAME dark lozenge on every desktop |
| 1306 |
* theme, which is why these two are flat values and not derived |
| 1307 |
* from anything. That is right for one line of text pinned to a |
| 1308 |
* control, and wrong for a rich card: the My WordPress entity |
| 1309 |
* hover card used to read them and showed up Obsidian over a white |
| 1310 |
* Legacy window. It has its own derived family now — |
| 1311 |
* `--os-my-wordpress-card-*`, further down — and it still names |
| 1312 |
* these two as its last fallback. |
| 1313 |
*/ |
| 1314 |
--os-tooltip-bg: #33303a; |
| 1315 |
--os-tooltip-fg: #fffbff; |
| 1316 |
|
| 1317 |
/* |
| 1318 |
* ---- Dock -------------------------------------------------- |
| 1319 |
* |
| 1320 |
* Void glass over the desk, with a Starlight hairline. The tile |
| 1321 |
* hover wash and the focus ring are the dock's identity moment: |
| 1322 |
* Pulse, at the two alphas that read as "warm" and "here". |
| 1323 |
* |
| 1324 |
* `--os-dock-icon-color` is a COLOUR, not a fill, and |
| 1325 |
* that is load-bearing: every image glyph in the dock is painted |
| 1326 |
* as a mask filled with this colour — a theme's own iconset via |
| 1327 |
* `"iconColor": "currentColor"`, and plugin / CPT artwork via |
| 1328 |
* `currentColor` on the tile. One token drives dashicons, theme |
| 1329 |
* art, plugin art, and the hover transition between them. |
| 1330 |
* |
| 1331 |
* Consumers: dock.css, dock-peek.css (which re-states the hover |
| 1332 |
* rule and so must read the same two tokens). |
| 1333 |
*/ |
| 1334 |
--os-dock-width: 56px; |
| 1335 |
--os-dock-icon-size: 20px; |
| 1336 |
/* |
| 1337 |
* The indicator line a dynamic dock collapses into while parked |
| 1338 |
* (Preferences → Appearance → Desktop layout → Dock behavior): |
| 1339 |
* the iOS home indicator, painted in the accent at partial alpha |
| 1340 |
* so it reads as a mark on the wallpaper rather than a control. |
| 1341 |
* `-length` runs along the rail's edge, `-thickness` across it; a |
| 1342 |
* theme retunes any of the three. |
| 1343 |
*/ |
| 1344 |
--os-dock-indicator-length: 180px; |
| 1345 |
--os-dock-indicator-thickness: 5px; |
| 1346 |
--os-dock-indicator-bg: color-mix( in srgb, var( --os-ui-accent, #f252fc ) 72%, transparent ); |
| 1347 |
--os-dock-bg: rgba(12, 11, 15, 0.72); |
| 1348 |
--os-dock-icon-color: rgba(255, 251, 255, 0.72); |
| 1349 |
--os-dock-icon-color-hover: #fffbff; |
| 1350 |
--os-dock-item-bg-hover: rgba(242, 82, 252, 0.18); |
| 1351 |
/* |
| 1352 |
* The status indicator and the focus ring, and both say "this |
| 1353 |
* one" about a tile the user chose — so they read the accent |
| 1354 |
* rather than a fixed Pulse. Pulse is still what an untouched |
| 1355 |
* install shows, because that is what the picker starts on. |
| 1356 |
*/ |
| 1357 |
--os-dock-item-outline: var(--os-ui-accent, #f252fc); |
| 1358 |
/* |
| 1359 |
* Hairline between the dock and the desktop. Reaches the side |
| 1360 |
* placements (as a single inline-edge border) AND the floating |
| 1361 |
* bottom pill (as its full outline). Set `transparent` for a |
| 1362 |
* borderless dock. |
| 1363 |
* |
| 1364 |
* The bottom pill's own chrome is separately overridable, because |
| 1365 |
* it is deliberately a different piece of glass — a warmer tint, a |
| 1366 |
* brighter top edge, an inset highlight, a drop shadow. Each falls |
| 1367 |
* back to the shared value above it. |
| 1368 |
*/ |
| 1369 |
--os-dock-border: rgba(255, 251, 255, 0.1); |
| 1370 |
|
| 1371 |
/* |
| 1372 |
* The dividers INSIDE the rail, which are a different job from the |
| 1373 |
* outline around it: they separate tiles that belong to different |
| 1374 |
* groups — core menus, plugin apps, and OpenStation's own controls. |
| 1375 |
* |
| 1376 |
* One treatment for all of them. An earlier pass gave the |
| 1377 |
* WordPress-to-OpenStation boundary Pulse and dropped the |
| 1378 |
* core-to-plugin one to a hairline, on the theory that only one |
| 1379 |
* boundary was worth reading. Two weights in one short rail read as |
| 1380 |
* two unrelated ideas instead of one system, so both are now the |
| 1381 |
* same line: Pulse at the waist, falling away to nothing at both |
| 1382 |
* ends, with a soft glow to hold it against the dock tint. |
| 1383 |
* |
| 1384 |
* Resolved one step back from the accent through |
| 1385 |
* `--os-ui-accent-dim`, where every ambient use of Pulse resolves, |
| 1386 |
* so "tone the station down" stays one edit. |
| 1387 |
*/ |
| 1388 |
--os-dock-divider: color-mix(in srgb, var(--os-ui-accent-dim) 70%, transparent); |
| 1389 |
--os-dock-floating-bg: rgba(12, 11, 15, 0.62); |
| 1390 |
--os-dock-floating-border: rgba(255, 251, 255, 0.12); |
| 1391 |
--os-dock-floating-border-top: rgba(255, 251, 255, 0.18); |
| 1392 |
--os-dock-floating-highlight: rgba(255, 251, 255, 0.1); |
| 1393 |
--os-dock-floating-shadow: rgba(0, 0, 0, 0.55); |
| 1394 |
|
| 1395 |
/* |
| 1396 |
* The phone layer (`mobile.css`). Its surfaces are the dock's |
| 1397 |
* family — translucent glass over the wallpaper, light glyphs — |
| 1398 |
* and read the dock tokens above for fill, text and lines. What |
| 1399 |
* the dock has no word for is declared here: the glass a tile, a |
| 1400 |
* round control and a switcher card are cut from, its pressed |
| 1401 |
* state, the shadow under a tile, the scrim behind the switcher, |
| 1402 |
* and the label shadow that keeps text legible over any wallpaper. |
| 1403 |
* A desktop theme that reskins the dock reskins the phone with it; |
| 1404 |
* one that wants the phone alone has these. |
| 1405 |
*/ |
| 1406 |
--os-mobile-glass: rgba(255, 251, 255, 0.1); |
| 1407 |
--os-mobile-glass-strong: rgba(255, 251, 255, 0.16); |
| 1408 |
--os-mobile-glass-border: rgba(255, 251, 255, 0.14); |
| 1409 |
--os-mobile-tile-shadow: 0 8px 20px rgba(0, 0, 0, 0.35); |
| 1410 |
--os-mobile-card-shadow: 0 -8px 24px rgba(0, 0, 0, 0.4); |
| 1411 |
--os-mobile-sheet-shadow: 0 -12px 40px rgba(0, 0, 0, 0.45); |
| 1412 |
--os-mobile-window-shadow: 0 12px 32px rgba(0, 0, 0, 0.45); |
| 1413 |
--os-mobile-scrim: rgba(0, 0, 0, 0.55); |
| 1414 |
--os-mobile-top-scrim: rgba(0, 0, 0, 0.45); |
| 1415 |
--os-mobile-label-shadow: 0 1px 2px rgba(0, 0, 0, 0.6); |
| 1416 |
|
| 1417 |
/* |
| 1418 |
* ---- The OpenStation layout --------------------------------- |
| 1419 |
* |
| 1420 |
* The constellation: the flyout that fans a menu's submenu out of |
| 1421 |
* its tile on hover, on every rail in every layout. The rail's |
| 1422 |
* divider used to live here too; it is shared chrome now and reads |
| 1423 |
* through `--os-dock-divider`. |
| 1424 |
* |
| 1425 |
* The constellation's SURFACE is Obsidian, deliberately. The mesh |
| 1426 |
* is spent on the row under the pointer and on the head's icon |
| 1427 |
* halo — the two moments where the panel is answering the user — |
| 1428 |
* and nowhere else. A flyout that was iridescent edge to edge |
| 1429 |
* would have nothing left to say when you actually pointed at |
| 1430 |
* something in it. |
| 1431 |
*/ |
| 1432 |
--os-cn-surface: rgba(26, 23, 33, 0.82); |
| 1433 |
--os-cn-border: rgba(255, 251, 255, 0.14); |
| 1434 |
--os-cn-shadow: 0 24px 64px rgba(0, 0, 0, 0.62), |
| 1435 |
0 2px 8px rgba(0, 0, 0, 0.4); |
| 1436 |
--os-cn-fg: #fffbff; |
| 1437 |
--os-cn-fg-muted: rgba(255, 251, 255, 0.62); |
| 1438 |
--os-cn-legend: rgba(255, 251, 255, 0.4); |
| 1439 |
--os-cn-divider: rgba(255, 251, 255, 0.1); |
| 1440 |
/* The row under the pointer — the panel's identity moment. */ |
| 1441 |
--os-cn-row-fill: var(--os-ui-holo-fill); |
| 1442 |
--os-cn-row-ink: var(--os-ui-holo-ink); |
| 1443 |
/* Beam: the thread from the panel's underside down to the tile. */ |
| 1444 |
--os-cn-beam: color-mix(in srgb, var(--os-ui-accent-dim) 80%, transparent); |
| 1445 |
--os-cn-radius: 14px; |
| 1446 |
/* |
| 1447 |
* Above every window and above the dock. Two panels coexist while |
| 1448 |
* the pointer moves along the rail — one dismissing, one arriving |
| 1449 |
* — and the retiring one is painted one step below so it can |
| 1450 |
* never fade out on top of the menu being read. |
| 1451 |
*/ |
| 1452 |
--os-cn-z: 2147483000; |
| 1453 |
|
| 1454 |
/* |
| 1455 |
* ---- Shell surfaces ---------------------------------------- |
| 1456 |
* |
| 1457 |
* The panels, tab strips and washes that belong to the shell |
| 1458 |
* rather than to the component kit. Same Obsidian-on-Void |
| 1459 |
* composition; the selection wash is Pulse. |
| 1460 |
*/ |
| 1461 |
--os-accent: #f252fc; |
| 1462 |
--os-link: #ec9bff; |
| 1463 |
--os-danger: #ff5a5a; |
| 1464 |
--os-border: rgba(255, 251, 255, 0.1); |
| 1465 |
--os-hover: rgba(255, 251, 255, 0.06); |
| 1466 |
--os-selected: rgba(242, 82, 252, 0.18); |
| 1467 |
--os-fg-muted: rgba(255, 251, 255, 0.7); |
| 1468 |
/* |
| 1469 |
* Shell text. Undeclared before the brand and it had to be: it read |
| 1470 |
* light on the desk (tile labels over the wallpaper) and dark |
| 1471 |
* inside a window, and one value broke one of the two. The station |
| 1472 |
* settles the argument — every surface it owns is dark now, so |
| 1473 |
* Starlight is right in both places. |
| 1474 |
*/ |
| 1475 |
--os-fg: #fffbff; |
| 1476 |
/* |
| 1477 |
* "…on light" is a name from before the station, and it is now a |
| 1478 |
* misnomer worth keeping: every surface that reads it — the folder |
| 1479 |
* window, its preview pane, the upload HUD — was a light card and |
| 1480 |
* is Obsidian today. The token means "text on the surfaces this one |
| 1481 |
* names", and those surfaces are dark, so the text is Starlight. |
| 1482 |
* Renaming it is a public-API change for the sake of tidiness; the |
| 1483 |
* comment is cheaper and the behaviour is what matters. |
| 1484 |
*/ |
| 1485 |
--os-fg-on-light: #fffbff; |
| 1486 |
--os-panel-bg: #1a1721; |
| 1487 |
--os-panel-header-bg: rgba(255, 251, 255, 0.04); |
| 1488 |
--os-folder-window-bg: #1a1721; |
| 1489 |
--os-my-wordpress-bg: #1a1721; |
| 1490 |
--os-my-wordpress-fg: #fffbff; |
| 1491 |
--os-my-wordpress-surface: rgba(255, 251, 255, 0.06); |
| 1492 |
/* |
| 1493 |
* The entity hover card — the "thumb" that floats over a tile with |
| 1494 |
* a title, a featured image and an excerpt. |
| 1495 |
* |
| 1496 |
* It is NOT a dock chip, and it used to be painted as one. |
| 1497 |
* `--os-tooltip-bg` is a fixed dark lozenge on every theme by |
| 1498 |
* design — one line of text, always the same object, no reason to |
| 1499 |
* follow anything. The card borrowed it, so a light desktop theme |
| 1500 |
* summoned an Obsidian card over a white window, with a border in |
| 1501 |
* `--os-ui-border` and an excerpt in `--os-ui-fg-muted` that both |
| 1502 |
* followed the WINDOW instead. Three families, one surface. |
| 1503 |
* |
| 1504 |
* The card is window furniture: it belongs to the surface it was |
| 1505 |
* summoned from, so it follows the theme that paints that surface. |
| 1506 |
* Every value below is DERIVED rather than declared flat, which is |
| 1507 |
* what makes that true — a theme that names only |
| 1508 |
* `--os-my-wordpress-bg` (Legacy names exactly that, `#fff`) moves |
| 1509 |
* the card with the window for free, and a theme that wants the |
| 1510 |
* card alone names a `-card-` token. |
| 1511 |
* |
| 1512 |
* A card lands on the same colour as the window under it, so the |
| 1513 |
* border and the shadow are the whole reason it reads as a |
| 1514 |
* separate object. Neither is decoration here and neither may |
| 1515 |
* collapse into the background — which is exactly what the border |
| 1516 |
* did: `--os-ui-border` is #33303a on this palette, the SAME value |
| 1517 |
* `--os-tooltip-bg` had, so the card had no edge at all. |
| 1518 |
* |
| 1519 |
* The shadow is the one flat value in the family. A drop shadow is |
| 1520 |
* cast light, dark on a light theme and dark on a dark one, so |
| 1521 |
* there is no window token for it to follow; it is named so a |
| 1522 |
* theme can still reach it. |
| 1523 |
*/ |
| 1524 |
--os-my-wordpress-card-bg: var(--os-my-wordpress-bg, #1a1721); |
| 1525 |
--os-my-wordpress-card-fg: var(--os-my-wordpress-fg, #fffbff); |
| 1526 |
--os-my-wordpress-card-fg-muted: var(--os-ui-fg-muted, #b3afb5); |
| 1527 |
--os-my-wordpress-card-border: var(--os-ui-border, #33303a); |
| 1528 |
--os-my-wordpress-card-shadow: 0 8px 28px rgba(0, 0, 0, 0.45); |
| 1529 |
--os-my-wordpress-card-thumb-bg: var( |
| 1530 |
--os-media-tile-bg, |
| 1531 |
rgba(255, 251, 255, 0.05) |
| 1532 |
); |
| 1533 |
--os-my-wordpress-card-lock-bg: var( |
| 1534 |
--os-ui-badge-danger-bg, |
| 1535 |
rgba(255, 90, 90, 0.16) |
| 1536 |
); |
| 1537 |
--os-ai-panel-bg: rgba(26, 23, 33, 0.97); |
| 1538 |
/* |
| 1539 |
* ---- Window tab strip --------------------------------------- |
| 1540 |
* |
| 1541 |
* A window with sub-pages reads as three surfaces stacked in |
| 1542 |
* depth, and the values below are that ramp: Astro on the focused |
| 1543 |
* title bar, VOID for the track the tabs sit in, then the page |
| 1544 |
* itself. The track is the darkest of the three on purpose — it |
| 1545 |
* has to stay a distinct band under BOTH title-bar states, and |
| 1546 |
* Obsidian would collapse into the unfocused bar (also Obsidian) |
| 1547 |
* exactly when a window has the least going on to distinguish it. |
| 1548 |
* |
| 1549 |
* The active tab is not a colour, it is the page arriving early. |
| 1550 |
* `chromeless.css` paints every admin page inside a window `#fff` |
| 1551 |
* whatever the admin colour scheme says, so the tab can name that |
| 1552 |
* white and the joint between the two is seamless. Retinting the |
| 1553 |
* tab means retinting the page it belongs to, and these two move |
| 1554 |
* together or the seam comes back. |
| 1555 |
* |
| 1556 |
* `-color-muted` is the second tone anything nested in an active |
| 1557 |
* tab needs — the external tab's detach and close chips. It is |
| 1558 |
* the only reason a "muted on light" value exists this far down a |
| 1559 |
* dark palette. |
| 1560 |
*/ |
| 1561 |
--os-tabs-bg: #1a1721; |
| 1562 |
/* |
| 1563 |
* The track on an UNFOCUSED window, which follows the title bar |
| 1564 |
* down to Void rather than holding Obsidian. |
| 1565 |
* |
| 1566 |
* A focused window already reads as two surfaces: title bar and |
| 1567 |
* track are the same Obsidian, and the tab lifts out of them. Let |
| 1568 |
* the track keep that Obsidian while the bar above it dims and |
| 1569 |
* the window reads as THREE, with the strip belonging to neither |
| 1570 |
* the chrome above nor the page below. Following the bar down |
| 1571 |
* keeps the count at two in both states. |
| 1572 |
* |
| 1573 |
* Both tracks read this: the shell's strip on an iframe window, |
| 1574 |
* and `<os-tabs variant="window">` inside a native one. The track |
| 1575 |
* is chrome in both cases, so it dims with the chrome; what keeps |
| 1576 |
* the tab attached to the content while that happens is the |
| 1577 |
* plate's fill, which wears the body's own colour rather than the |
| 1578 |
* track's. |
| 1579 |
* |
| 1580 |
* Note the asymmetry with the title bar's pair, which is |
| 1581 |
* deliberate: there, `--os-titlebar-bg` is the unfocused base and |
| 1582 |
* `-focused` is the modifier. Here the base is the LIT value, |
| 1583 |
* so a theme naming one track colour lands on the state where the |
| 1584 |
* track is doing the most work. |
| 1585 |
* |
| 1586 |
* A theme that sets only `--os-tabs-bg` (Legacy, and anything |
| 1587 |
* written before this token existed) resolves through it in both |
| 1588 |
* states and keeps its single strip colour. |
| 1589 |
*/ |
| 1590 |
--os-tabs-bg-unfocused: #0c0b0f; |
| 1591 |
--os-tabs-color: #b3afb5; |
| 1592 |
--os-tabs-active-bg: #fff; |
| 1593 |
--os-tabs-active-color: #0c0b0f; |
| 1594 |
--os-tabs-active-color-muted: rgba(12, 11, 15, 0.6); |
| 1595 |
/* |
| 1596 |
* The plate's own body: a frosted crown resolving to flat page |
| 1597 |
* white well before the joint. |
| 1598 |
* |
| 1599 |
* Every stop is OPAQUE, and that is a requirement rather than a |
| 1600 |
* preference. The face used to be translucent over a |
| 1601 |
* `backdrop-filter`, which promotes it to its own compositor layer |
| 1602 |
* and leaves a faint grey hairline where that layer is clipped — |
| 1603 |
* down the plate's sides and across its bottom, which is precisely |
| 1604 |
* where this design has a bright rail and needs everything else to |
| 1605 |
* be invisible. |
| 1606 |
* |
| 1607 |
* The last stop must also land above the joint (the bottom |
| 1608 |
* `--os-tabs-radius` of the plate), because the joint is painted |
| 1609 |
* in flat `--os-tabs-active-bg` and a body still tinted where the |
| 1610 |
* two meet draws a seam of its own. If you retune these stops, |
| 1611 |
* check the bottom edge first. |
| 1612 |
*/ |
| 1613 |
--os-tabs-active-frost: linear-gradient( |
| 1614 |
180deg, |
| 1615 |
#f4eff9 0%, |
| 1616 |
#ffffff 58% |
| 1617 |
); |
| 1618 |
/* |
| 1619 |
* The crown. Holomesh, masked away before the joint for the same |
| 1620 |
* reason. It is on exactly ONE tab at a time — that is what keeps |
| 1621 |
* the mesh an identity moment instead of wallpaper, and it is the |
| 1622 |
* rule the rest of the kit follows. Set it to `none` to get the |
| 1623 |
* plain frosted plate back. |
| 1624 |
*/ |
| 1625 |
--os-tabs-active-crown: var(--os-mesh-holo); |
| 1626 |
--os-tabs-active-crown-opacity: 0.3; |
| 1627 |
/* |
| 1628 |
* The rail: one continuous line around the silhouette of |
| 1629 |
* page-plus-tab. |
| 1630 |
* |
| 1631 |
* This is the one place the accent is spent on the tab strip, and |
| 1632 |
* spending it here is what lets the tab itself stay uncoloured — |
| 1633 |
* so it is the accent the user picked, flat, and not Pulsemesh. |
| 1634 |
* A mesh here would be the accent everywhere else on the tab |
| 1635 |
* strip disagreeing with the one line that carries it. Written as |
| 1636 |
* a gradient rather than a colour because the rail is painted as |
| 1637 |
* a background-image through a mask. |
| 1638 |
* |
| 1639 |
* Set it to `none` for the plain frosted plate with no line. |
| 1640 |
*/ |
| 1641 |
--os-tabs-rail: linear-gradient( |
| 1642 |
var(--os-ui-accent, #f252fc), |
| 1643 |
var(--os-ui-accent, #f252fc) |
| 1644 |
); |
| 1645 |
--os-tabs-rail-width: 2px; |
| 1646 |
--os-media-tile-bg: rgba(255, 251, 255, 0.05); |
| 1647 |
--os-media-visual-bg: rgba(255, 251, 255, 0.04); |
| 1648 |
--os-skeleton-low: rgba(255, 251, 255, 0.05); |
| 1649 |
--os-skeleton-high: rgba(255, 251, 255, 0.13); |
| 1650 |
--os-drop-preview-bg: rgba(242, 82, 252, 0.1); |
| 1651 |
--os-drop-preview-border: rgba(242, 82, 252, 0.55); |
| 1652 |
|
| 1653 |
/* |
| 1654 |
* File tiles — anywhere a `.os-file-tile` (or sibling |
| 1655 |
* canvas tile) renders. The defaults match the desk: Starlight |
| 1656 |
* labels over a dark sky, with a Pulse selection wash. |
| 1657 |
* |
| 1658 |
* Surfaces that are light in their own right override these in |
| 1659 |
* their own scope, e.g.: |
| 1660 |
* |
| 1661 |
* .desktop-mode-folder-window { |
| 1662 |
* --os-tile-fg: #1d2327; |
| 1663 |
* --os-tile-hover-bg: rgba(0, 0, 0, 0.06); |
| 1664 |
* } |
| 1665 |
* |
| 1666 |
* Plugin authors can override any of these in their own theme |
| 1667 |
* to retint tiles globally without touching the rules below. |
| 1668 |
*/ |
| 1669 |
--os-tile-fg: var(--os-fg, #fffbff); |
| 1670 |
--os-tile-fg-muted: rgba(255, 251, 255, 0.7); |
| 1671 |
--os-tile-hover-bg: rgba(255, 251, 255, 0.12); |
| 1672 |
--os-tile-selected-bg: rgba(242, 82, 252, 0.24); |
| 1673 |
--os-tile-focus-ring: var(--wp-admin-theme-color, #f252fc); |
| 1674 |
--os-tile-shortcut-bg: rgba(12, 11, 15, 0.7); |
| 1675 |
--os-tile-shortcut-fg: #fffbff; |
| 1676 |
--os-tile-shortcut-shadow: 0 1px 3px rgba(0, 0, 0, 0.6); |
| 1677 |
|
| 1678 |
/* |
| 1679 |
* Label rendering tokens. The desk is dark at every wallpaper, so |
| 1680 |
* a soft drop-shadow boosts legibility against the artwork, |
| 1681 |
* regular weight, default antialiasing. |
| 1682 |
* |
| 1683 |
* Light-context surfaces (folder windows, My WordPress, any |
| 1684 |
* future window with a light body) rebind these in their own |
| 1685 |
* scope so tile labels render with the same crispness as the |
| 1686 |
* surrounding chrome — no per-surface duplicate rules. |
| 1687 |
*/ |
| 1688 |
--os-tile-label-shadow: 0 1px 2px rgba(0, 0, 0, 0.6); |
| 1689 |
--os-tile-label-weight: 400; |
| 1690 |
--os-tile-label-smoothing: auto; |
| 1691 |
--os-tile-label-color: var(--os-tile-fg); |
| 1692 |
|
| 1693 |
/* |
| 1694 |
* Admin bar — how many pixels of the bar stay on screen while it |
| 1695 |
* is parked off the top edge in `dynamic` mode. This is the |
| 1696 |
* VISIBLE seam only: small enough to read as "nothing is there". |
| 1697 |
* Themes may retune it; `0` makes the bar invisible until hovered. |
| 1698 |
*/ |
| 1699 |
--os-admin-bar-peek: 4px; |
| 1700 |
|
| 1701 |
/* |
| 1702 |
* How far BELOW the parked bar the invisible reveal zone reaches. |
| 1703 |
* Decoupled from the peek on purpose — the seam wants to be a |
| 1704 |
* hairline, the pointer target wants to be forgiving, and tying |
| 1705 |
* them together forces one of the two to be wrong. The band the |
| 1706 |
* user actually has to hit is `peek + this`. |
| 1707 |
* |
| 1708 |
* CEILING: keep `peek + reveal-zone` comfortably under the admin |
| 1709 |
* bar's own height (32px, 46px below 783px). Past that, leaving |
| 1710 |
* the revealed bar drops the pointer straight back into the zone, |
| 1711 |
* which re-reveals it — an oscillation loop, not a wider target. |
| 1712 |
*/ |
| 1713 |
--os-admin-bar-reveal-zone: 16px; |
| 1714 |
|
| 1715 |
/* Z-index layers */ |
| 1716 |
--os-z-base: 100; |
| 1717 |
--os-z-dock: 200; |
| 1718 |
--os-z-adminbar: 9991; |
| 1719 |
--os-z-fullscreen: 99999; |
| 1720 |
/* Window-link layer — above widgets (z 1), behind windows (z 100+). */ |
| 1721 |
--os-z-window-links: 50; |
| 1722 |
/* |
| 1723 |
* Mio layer — above every window (windows run 100 + stack |
| 1724 |
* index) so the companion can perch on top of them, but below |
| 1725 |
* the dock (200) so it never covers navigation. |
| 1726 |
*/ |
| 1727 |
--os-z-mio: 190; |
| 1728 |
/* |
| 1729 |
* The desktop-name caption. Same reasoning as Mio, one step up: |
| 1730 |
* above every window so a maximized Dashboard cannot hide it, and |
| 1731 |
* above the companion, since a momentary message should not be |
| 1732 |
* the thing that gets perched on. Still under the dock (200). |
| 1733 |
*/ |
| 1734 |
--os-z-desktop-name: 195; |
| 1735 |
/* |
| 1736 |
* The notch — on the desk, under the windows (100 + stack index), |
| 1737 |
* above the window-link wires (50) so a tie never draws across the |
| 1738 |
* pill. It hangs over the strip a window's title bar occupies, and |
| 1739 |
* a pill floating above someone's window is the shell talking over |
| 1740 |
* the thing they are working in. |
| 1741 |
*/ |
| 1742 |
--os-z-notch: 60; |
| 1743 |
|
| 1744 |
/* |
| 1745 |
* Window-link ties (relation splines between windows). The accent |
| 1746 |
* follows the admin color scheme. Solid colors only — the resting |
| 1747 |
* dimming is done with stroke-opacity/fill-opacity in |
| 1748 |
* window-links.css, NOT color-mix(): an unresolvable color-mix() |
| 1749 |
* inside a custom property makes the consuming declaration invalid |
| 1750 |
* at computed-value time, which turns SVG strokes invisible and |
| 1751 |
* marker fills black (the written rgba() fallback declaration is |
| 1752 |
* already gone from the cascade by then). Overridable per scheme |
| 1753 |
* or by plugins/themes without touching the renderer. |
| 1754 |
*/ |
| 1755 |
--os-window-link-color: var(--wp-admin-theme-color, #f252fc); |
| 1756 |
--os-window-link-color-active: var(--wp-admin-theme-color, #f252fc); |
| 1757 |
--os-window-link-width: 1.5px; |
| 1758 |
--os-window-link-accent: var(--wp-admin-theme-color, #f252fc); |
| 1759 |
/* |
| 1760 |
* Halo behind related windows (`.os-window--linked`). |
| 1761 |
* A literal rgba of Pulse rather than a color-mix() of the accent — |
| 1762 |
* same no-color-mix rationale as above: if this token failed to |
| 1763 |
* resolve, the whole box-shadow declaration (elevation shadow |
| 1764 |
* included) would go invalid. Schemes/plugins that retint the |
| 1765 |
* accent should override this too. |
| 1766 |
*/ |
| 1767 |
--os-window-link-glow: rgba(242, 82, 252, 0.45); |
| 1768 |
} |
| 1769 |
|
| 1770 |
/* |
| 1771 |
* ---- Iframe windows keep a light body ----------------------------- |
| 1772 |
* |
| 1773 |
* A window hosting a real `wp-admin` page is not a station surface — it |
| 1774 |
* is a frame around someone else's document, and that document is |
| 1775 |
* light. The reveal surface is what covers such a window while it |
| 1776 |
* loads, so a dark one wiping back to a white page is a flash in the |
| 1777 |
* wrong direction. |
| 1778 |
* |
| 1779 |
* The window's own background is deliberately NOT overridden here, and |
| 1780 |
* that was learned the hard way: `chromeless.css` paints the iframe's |
| 1781 |
* canvas, so nothing of the window shows through the page anyway — |
| 1782 |
* while the tab strip above it carries a 16px `mask-image` fade at |
| 1783 |
* each end (the "scroll for more tabs" affordance). A mask makes the |
| 1784 |
* element's own background transparent, so a white window behind a |
| 1785 |
* dark strip turned that invisible cosmetic into a white gradient |
| 1786 |
* bleeding into the chrome. The strip needs the station's colour |
| 1787 |
* behind it; the page needs its own; those are two different surfaces |
| 1788 |
* and only one of them belongs to the window element. |
| 1789 |
* |
| 1790 |
* Native windows — the ones the station draws itself — are excluded |
| 1791 |
* and keep the Obsidian reveal from the palette above. |
| 1792 |
*/ |
| 1793 |
.os-window:not( .os-window--native ) { |
| 1794 |
--os-window-reveal-surface: #fff; |
| 1795 |
} |
| 1796 |
|
| 1797 |
/* |
| 1798 |
* ---- The WordPress admin colour scheme no longer tints the shell ---- |
| 1799 |
* |
| 1800 |
* There used to be nine blocks here, one per admin colour scheme, each |
| 1801 |
* setting `--wp-admin-theme-color` on |
| 1802 |
* `.os-shell[data-os-scheme="…"]`. They are gone, |
| 1803 |
* and their removal is a bug fix as much as a rebrand. |
| 1804 |
* |
| 1805 |
* OS Settings → Appearance writes the user's chosen accent as an inline |
| 1806 |
* style on `<html>` — deliberately, so it also reaches the WordPress |
| 1807 |
* admin bar, which is a SIBLING of `#os-shell`. But those |
| 1808 |
* blocks matched the shell root, a descendant of `<html>`, and for |
| 1809 |
* custom properties the nearest ancestor with a value wins no matter |
| 1810 |
* what the specificity of the rule that set it was. So inside the shell |
| 1811 |
* the scheme always beat the picker: choosing Rose, or Pulse, changed |
| 1812 |
* the admin bar and nothing else. Every focus ring, tab underline, sort |
| 1813 |
* arrow and selection wash kept the colour of the admin scheme. |
| 1814 |
* |
| 1815 |
* With the accent picker defaulting to Pulse there is nothing left for |
| 1816 |
* these blocks to express: the station has one identity colour, and a |
| 1817 |
* user who wants their admin scheme's hue picks it in the same panel. |
| 1818 |
* The `data-os-scheme` attribute is still stamped on the |
| 1819 |
* shell root for plugins and themes that key off it. |
| 1820 |
*/ |
| 1821 |
|
| 1822 |
/* The chat is a MIO surface even when its owning window wears a light theme. |
| 1823 |
* Component colours remain reachable through the public MIO token family. */ |
| 1824 |
body.os-active .os-mio-chat, |
| 1825 |
body.os-active .os-mio-chat-launcher { |
| 1826 |
--os-ui-fg: var(--os-mio-chat-fg, #1d2327); |
| 1827 |
--os-ui-fg-muted: var(--os-mio-chat-muted, #646970); |
| 1828 |
--os-window-bg: var(--os-mio-chat-bg, #fff); |
| 1829 |
--os-ui-border: var(--os-mio-chat-border, #c3c4c7); |
| 1830 |
} |
| 1831 |
|
| 1832 |
/* Ghost labels sit on the chat; the hero button owns a lighter mesh. */ |
| 1833 |
body.os-active .os-mio-chat os-button[variant="ghost"], |
| 1834 |
body.os-active .os-mio-chat-launcher { |
| 1835 |
--os-ui-button-fg: var(--os-mio-chat-fg, #1d2327); |
| 1836 |
--os-ui-button-bg-hover: var(--os-mio-chat-hover-bg, #f0f0f1); |
| 1837 |
} |
| 1838 |
|
| 1839 |
body.os-active .os-mio-chat os-button[variant="primary"], |
| 1840 |
body.os-active .os-mio-chat os-button[variant="holo"] { |
| 1841 |
--os-ui-button-fg: var(--os-ui-holo-ink, #1d2327); |
| 1842 |
} |
| 1843 |
|
| 1844 |
/* The component owns the launcher's single border and rounded surface. */ |
| 1845 |
body.os-active .os-mio-chat-launcher { |
| 1846 |
--os-ui-button-bg: var(--os-mio-launcher-bg, #ffffffa0); |
| 1847 |
--os-ui-button-border: 1px solid var(--os-mio-chat-border, #c3c4c7); |
| 1848 |
--os-ui-button-border-radius: var(--os-mio-chat-radius, 22px); |
| 1849 |
} |
| 1850 |
|
| 1851 |
body.os-active .os-mio-callout { |
| 1852 |
--os-ui-button-border: 0; |
| 1853 |
--os-ui-button-border-radius: 50%; |
| 1854 |
--os-ui-button-padding: 0; |
| 1855 |
--os-ui-button-bg: transparent; |
| 1856 |
--os-ui-button-fg: var(--os-mio-callout-fg, #382b38); |
| 1857 |
--os-ui-button-bg-hover: color-mix(in srgb, var(--os-mio-callout-fg, #382b38) 10%, transparent); |
| 1858 |
} |
| 1859 |
|
