loopable / web /src /starred /starred.css
fsanyoto's picture
Deploy AIOS web (React glide grid + FastAPI slice)
7f72224 verified
Raw History Blame Contribute Delete
10.1 kB
/* ─────────────────────────────────────────────────────────────────────────────────────────
starred/starred.css β€” WAVE 35, owner item 8: the Starred module's OWN rules.
β›” WHAT IS NOT HERE IS THE POINT. The page box, the title, the section headings and the
whole tile family are Home's classes worn as-is, because DESIGN.md 2's sibling rule is
about RENDERED VALUES and the only way to hold two surfaces to identical values through a
wave that is actively editing the tile grid is to be the same rules. This file holds the
four things Home has no equivalent of: the type filter, the degraded sentence, the
loading box and the two chip glyphs.
⚠ NOTHING HERE REDEFINES A .home-*, .shell-* OR .cg-* RULE. `index.css` belongs to the
integrator for the whole wave, and a second definition of a shared class would be decided
by source order rather than by anybody's intent (`shell/navExtras.css`'s own header
records that this nav has already lost a rule that way once).
⚠ EVERY font-size IS A --lp-fs-* TOKEN: verify_ui globs every stylesheet under src.
───────────────────────────────────────────────────────────────────────────────────────── */
/* ── the type filter ────────────────────────────────────────────────────────────────────
It occupies the slot Home gives its list/grid toggle, but LEFT aligned, because this is a
primary control rather than a display preference: it decides what the page is about, and a
primary control on the far right of an empty row reads as an afterthought.
⚠ Starred deliberately has NO list/grid toggle. Home's exists because a recents list gets
long; a star list is short by construction, and a second display preference with its own
storage key is a control nobody asked for (owner item 8 names a type filter and nothing else). */
.st-bar {
display: flex;
align-items: center;
gap: 6px;
flex-wrap: wrap;
margin-bottom: 16px;
}
/* The quiet button shape DESIGN.md 4 names: muted ink, wash on hover, nothing else. The UA
chrome is reset explicitly here (border/background/font/color), which is the wave-19
"mystery outer lines and tinted fill" rule and is why `.home-card` and `.home-tile` do it too. */
.st-tab {
display: inline-flex;
align-items: center;
gap: 6px;
padding: 5px 11px;
border: 1px solid var(--lp-line);
border-radius: var(--lp-r-pill);
background: var(--lp-surface);
color: var(--lp-muted);
font: inherit;
font-size: var(--lp-fs-2xs);
font-weight: 600;
cursor: pointer;
transition: border-color 0.14s var(--lp-fold-e), background 0.14s var(--lp-fold-e);
}
.st-tab:hover {
background: var(--lp-surface-2);
border-color: var(--lp-blue-deep);
}
/* Blue = selected, the fixed semantic (DESIGN.md 3).
β›” THE INK GOES TO --lp-ink, NOT TO --lp-blue-deep, AND THAT WAS MEASURED OFF THE RENDER RATHER
THAN COPIED. `.home-layout-btn.is-on` paints `--lp-blue-deep` (#768fb6) on `--lp-blue-tint`
(#edf3fd), which is 2.96:1 β€” under the 4.5:1 TEXT bar and under the 3:1 graphical bar too. That
button holds only a 14px ICON; this pill holds a WORD, at 12.75px. Copying its colour pair would
have put the page's own filter labels below the floor.
The precedent that IS right is one control up: `.shell-nav-item.is-active` marks selection with
the tint plus WEIGHT and leaves the ink alone. Same here: tint, blue border, ink at 13.8:1. */
.st-tab.is-on {
background: var(--lp-blue-tint);
border-color: var(--lp-blue-deep);
color: var(--lp-ink);
}
/* The count is a subordinate number on a label, so it steps DOWN one size and one weight and
INHERITS the pill's ink. It never takes a colour of its own: this is a length, not a status.
⚠ NO `opacity` β€” the obvious way to subordinate it, and it fails the same measurement: muted
ink at 0.75 over white is 2.99:1. Size and weight do the same job and cost no contrast. */
.st-tab-count {
font-size: var(--lp-fs-3xs);
font-weight: 500;
font-variant-numeric: tabular-nums;
}
/* ── the degraded sentence ──────────────────────────────────────────────────────────────
A short list that says it may be short. Yellow is the fixed attention semantic; the DEEP
companion carries the text, because a pastel on white is not a light aesthetic, it is an
unreadable one (DESIGN.md 3). One containment layer, hairline, no shadow. */
.st-note {
margin: 0 0 16px;
padding: 9px 12px;
border: 1px solid var(--lp-yellow);
border-radius: var(--lp-r-md);
background: var(--lp-yellow-tint);
color: var(--lp-yellow-deep);
font-size: var(--lp-fs-2xs);
line-height: var(--lp-lh);
}
/* ── loading, and the way back from a failed read ───────────────────────────────────────
The mark is centred in a fixed band rather than at the top of an empty page: at 7,331 ms
cold this is on screen long enough to be looked at, and a spinner pinned to the top-left of
a blank surface reads as debris (index.css's own note beside `.lp-spin--lg`). */
.st-loading {
display: flex;
align-items: center;
justify-content: center;
min-height: 180px;
}
.st-failed {
display: flex;
align-items: center;
gap: 12px;
}
.st-retry {
padding: 5px 12px;
border: 1px solid var(--lp-line);
border-radius: var(--lp-r-md);
background: var(--lp-surface);
color: var(--lp-ink);
font: inherit;
font-size: var(--lp-fs-2xs);
font-weight: 600;
cursor: pointer;
}
.st-retry:hover {
background: var(--lp-surface-2);
border-color: var(--lp-blue-deep);
}
/* ── the star, on a tile ────────────────────────────────────────────────────────────────
β›” THE WRAPPER IS NOT DECORATION. A Home database tile is an `<a>` and an agent tile is a
`<button>`; a `<button>` nested in either is invalid HTML and needs `preventDefault` to stop
the click following the link. So the star is a SIBLING, and this box is what positions it.
⚠ THIS IS A NEW RULE, NOT A CHANGE TO `.home-tile`. `index.css` belongs to the integrator for
the whole wave. `.st-tilewrap > .home-tile` is scoped to this wrapper and cannot reach a tile
anywhere else in the app; `.home-tile`'s own rule is untouched, and the wrapper is what became
the grid item, so the tile still fills the cell exactly as it did. */
.st-tilewrap {
position: relative;
display: flex;
min-width: 0;
}
.st-tilewrap > .home-tile {
flex: 1 1 auto;
min-width: 0;
/* Room for the star, so a long name ellipses before it reaches the control rather than
sliding underneath it. */
padding-right: 38px;
}
/* Quiet, muted, wash on hover: DESIGN.md 4's quiet-button shape, with the UA chrome reset
explicitly (the wave-19 "mystery outer lines and tinted fill" rule). */
.st-star {
position: absolute;
top: 50%;
right: 10px;
transform: translateY(-50%);
display: inline-flex;
align-items: center;
justify-content: center;
width: 24px;
height: 24px;
padding: 0;
border: 0;
border-radius: var(--lp-r-sm);
background: transparent;
color: var(--lp-muted);
font: inherit;
cursor: pointer;
opacity: 0;
transition: opacity 0.14s var(--lp-fold-e), color 0.14s var(--lp-fold-e);
}
/* β›” THREE WAYS TO BE VISIBLE, AND ONLY ONE OF THEM IS THE POINTER.
Β· `:hover` on the wrapper reveals it on an unstarred tile, which is the reference behaviour;
Β· `.is-on` keeps it visible ALWAYS, because a page that hides which tiles are starred until
you sweep the pointer over them has not answered the question it exists to answer;
Β· `:focus-visible` reveals it for a keyboard, because a control that exists only under a
pointer is unreachable. D-253 is a booked defect whose entire content is "satisfied only on
hover"; this is that lesson applied to an affordance rather than to an explanation. */
.st-tilewrap:hover .st-star,
.st-star:focus-visible,
.st-star.is-on {
opacity: 1;
}
.st-star:hover {
color: var(--lp-yellow-deep);
}
/* Yellow is the fixed attention/brand-accent semantic (DESIGN.md 3), on the DEEP companion
because a pastel on white is unreadable. The filled star is the "this matters to me" mark. */
.st-star.is-on {
color: var(--lp-yellow-deep);
}
.st-star:disabled {
cursor: default;
opacity: 0.5;
}
/* A disabled star must not vanish mid-write: without this, `opacity: 0` from the base rule wins
back the moment the pointer leaves, and a click that is still in flight looks like nothing
happened. */
.st-star.is-on:disabled,
.st-tilewrap:hover .st-star:disabled {
opacity: 0.5;
}
/* ── the row count beside a starred view (R7 / C3) ──────────────────────────────────────
It sits on the tile's second line after the database name, so the line reads "which one, then
how big". Tabular figures: these numbers sit in a column across tiles and a proportional 1
makes that column wobble. */
.st-count {
margin-left: 7px;
padding-left: 7px;
border-left: 1px solid var(--lp-line);
font-variant-numeric: tabular-nums;
}
/* IconTile owns the frame; this rule paints only the query glyph. */
.st-chip-glyph {
width: 16px;
height: 16px;
fill: none;
stroke: currentColor;
stroke-width: 1.35;
stroke-linecap: round;
stroke-linejoin: round;
}