Watch
0
0
Fork
You've already forked hyperhive
0
hyperhive/frontend/packages/shared/src/theme.css
iris 1ca82b3e09 frontend: one glass token pair in place of three copied light and dark blocks
Headers, badges, terminal panes, the message box and the dashboard's bars read --glass-clear and --glass-filter from theme.css; the light palette (colors.css) and the solid-backgrounds setting set them. Each surface keeps a single rule, the per-theme override blocks and the quiet-badge specificity workaround go, and the dashboard and agent page now follow the light palette like the swarm UI.
2026-11-20 00:22:35 +01:00

87 lines
4.5 KiB
CSS

/* Semantic theme layer — derived from the base16 contract in
`colors.css`. This is what the app references (`--bg`, `--fg`,
`--purple`, …); page CSS must use these names, never literal colours
and never the raw `--baseNN` slots.
Standalone stylesheet, linked by every page right AFTER `colors.css`
(which defines the `--baseNN` slots these rules resolve against). Kept
separate from the page bundles — esbuild would otherwise inline an
`@import` and bake the palette into every CSS bundle.
A theme swap touches only `colors.css` (the 16 base16 slots); this
derivation layer never changes. See docs/4-implementation/web-ui/css-vars.md. */
:root {
--bg: var(--base00);
--bg-elev: var(--base01); /* elevated surfaces: dropdowns, popovers */
--border: var(--base02); /* general borders, hover/active backgrounds */
--purple-dim: var(--base03); /* subtle borders, terminal chrome, badge bg */
--fg: var(--base05);
--red: var(--base08); /* errors, fail state */
--amber: var(--base09); /* warnings, pending / running state */
--yellow: var(--base0A); /* flash messages, mild warnings */
--green: var(--base0B); /* success, ok state */
--cyan: var(--base0C); /* tool-use events, info accents */
--blue: var(--base0D); /* links, interactive accent (distinct from cyan) */
--purple: var(--base0E); /* accent — active tabs, links, highlights */
--pink: var(--base0F); /* thinking events */
/* Off-base16 (no exact slot) — derived from base16 so they still track
a swap. Each is pixel-identical to its prior literal under the
default palette: --crust is a darkened bg; --muted / --subtext0 are
foreground↔background blends (two levels of dimmed text). */
--crust: color-mix(
in srgb,
var(--base00) 58%,
#000000
); /* scrims and shadows: a darkened bg, in both themes */
/* The surface text sits on in a terminal or a code block. In the dark theme
it is `--crust`, below `--bg`. A light palette keeps nearly all of its
background (`--code-bg-share` in `colors.css`), as `--crust` is a mid
grey there and the text on it fell to 2:1. */
--code-bg: color-mix(
in srgb,
var(--base00) var(--code-bg-share, 58%),
#000000
);
--muted: color-mix(
in srgb,
var(--base05) var(--muted-share, 58%),
var(--base00)
); /* secondary / dimmed text */
--subtext0: color-mix(
in srgb,
var(--base05) var(--subtext0-share, 77.7%),
var(--base00)
); /* toolbar/status text; dimmer than --fg, lighter than --muted */
/* `--muted-share` and `--subtext0-share` are how much of the text colour each
mix keeps. A palette whose background is light sets them higher in
`colors.css`: at the dark palette's 58% the light one's muted text was
2.4:1 against its card background, short of the 4.5:1 AA asks for. A palette
that sets neither keeps the shares above. */
/* The frosted-glass surfaces (headers, badges, terminal panes, the message
box) are see-through over a blur on the dark palette and solid on the light
one, where bright content behind them would wash the text out.
`--glass-clear` is 1 for glass and 0 for solid; a surface keeps
`calc(100% - its-clear-share * var(--glass-clear))` of its fill colour, and
`--glass-filter` is its `backdrop-filter`. A light palette sets
`--palette-glass-clear` and `--palette-glass-filter` in `colors.css`, and
the solid-backgrounds setting sets the two final tokens itself. */
--glass-clear: var(--palette-glass-clear, 1);
--glass-filter: var(--palette-glass-filter, blur(8px) saturate(130%));
/* `--muted`, above, is mixed toward `--base00`/`--bg` — correct for
dimmed text on the page background, wrong for dimmed text sitting on
an elevated fill like `--purple-dim` (badge/dropdown-item
backgrounds). Case in point: `.ui-badge-label` used bare `--muted`
and mara measured it at ~1.3:1 against her theme's badge fill —
`--muted` had never been checked against anything but `--bg`. This
variant mixes toward the *actual* surface it sits on instead, same
technique, correct anchor. Ceiling note: even plain `--fg` (100% —
the max this can approach) only reaches ~3.4:1 against `--purple-dim`
in mara's theme, short of formal 4.5:1 AA for normal text — that's
the theme's own limit, not something the anchor choice can fix. 90%
gets close to that ceiling (~3:1, more than double the old ~1.3:1)
while keeping a hint of the label/value visual distinction. */
--muted-on-dim: color-mix(in srgb, var(--fg) 90%, var(--purple-dim));
}