loopable / web /src /styles /wave46 /rail-select.css
fsanyoto's picture
Deploy AIOS web (React glide grid + FastAPI slice)
6e31d07 verified
Raw History Blame
11 kB
/* WAVE 46 - T02. The views rail's multi-select bar and the selected-row mark.
*
* Loaded from ViewSidebar.tsx rather than from index.css (contract C6): an @imported sheet sits
* ABOVE index.css's own rules and loses every equal-specificity fight with them, so the
* selected-row background below would never beat `.cg-view-row.is-active`. A sheet imported from
* a component lands after index.css in the bundle and wins.
*
* Tokens only: no literal font-size, no inline hex. Blue marks the selection, red marks the one
* destructive control.
*/
.cg-railsel {
display: flex;
flex-wrap: wrap;
align-items: center;
gap: 8px;
padding: 8px 12px;
border-top: 1px solid var(--cg-line);
background: var(--lp-blue-tint);
color: var(--cg-text);
font-size: var(--lp-fs-2xs);
animation: cg-railsel-in 140ms ease-out;
}
@keyframes cg-railsel-in {
from { opacity: 0; transform: translateY(4px); }
to { opacity: 1; transform: none; }
}
@media (prefers-reduced-motion: reduce) {
.cg-railsel { animation: none; }
}
.cg-railsel-count {
flex: 1 1 auto;
min-width: 0;
font-weight: 600;
}
.cg-railsel-ask {
flex: 1 1 100%;
min-width: 0;
color: var(--cg-text);
}
/* Quiet buttons, same posture as `.shell-newfolder`: native chrome off, hairline border, no
* shadow. `font: inherit` keeps them on the bar's own step of the scale. */
.cg-railsel button {
border: 0;
background: transparent;
font: inherit;
color: inherit;
box-shadow: inset 0 0 0 1px var(--cg-line);
border-radius: 6px;
padding: 4px 8px;
cursor: pointer;
transition: opacity 120ms ease-out, background 120ms ease-out;
}
.cg-railsel button:hover:not(:disabled) {
box-shadow: inset 0 0 0 1px var(--lp-blue-deep);
background: var(--lp-wash);
}
.cg-railsel button:focus-visible {
outline: 2px solid var(--lp-blue-deep);
outline-offset: 1px;
}
.cg-railsel button:disabled {
opacity: 0.5;
cursor: default;
}
.cg-railsel button.is-danger {
color: var(--lp-red-deep);
box-shadow: inset 0 0 0 1px var(--lp-red-deep);
}
.cg-railsel button.is-danger:hover:not(:disabled) {
background: var(--lp-red-tint);
box-shadow: inset 0 0 0 1px var(--lp-red-deep);
}
/* The rows in the range. Kept distinct from `.is-active`, which says "this is the table you are
* looking at" and can be true of a selected row at the same time. */
.cg-view-row.is-railsel {
background: var(--lp-blue-tint);
box-shadow: inset 2px 0 0 var(--lp-blue-deep);
}
/* WAVE 46 - T03. The bulk-export list's rows, on the panel's own step of the scale.
*
* OWNER RULING 2026-08-29, and it AMENDS the ticket's literal done-when. That clause asked for
* "the same computed font-size as the sibling rail rows", and the rail is TWO answers, neither of
* them the right target: the `.cg-view-row` element itself declares nothing and computes the 17px
* root, while the text you actually read sits in `.cg-view-main`, which declares `--lp-fs-xs`.
* Chasing the first leaves these rows exactly as they were, which is the complaint. The owner
* chose the other target instead: the whole export PANEL reads at ONE size. So these rows take
* `--lp-fs-2xs`, the step `.cg-pop-title` and `.cg-pop-note` already use beside them, and they
* deliberately DIFFER from the rail by one step.
*
* ⛔ SO THE RULED ANSWER IS `--lp-fs-2xs` AND NOT `--lp-fs-xs`, and that is the correction a later
* reader will actually reach for: reading the done-when literally against `.cg-view-main` argues
* for `--lp-fs-xs`, which is a real and plausible-looking target one step above this one. It was
* considered and rejected. Matching the PANEL beat matching the rail, because the two lines this
* list sits directly under are `--lp-fs-2xs` and the jump inside one small panel is the whole
* complaint. Do not move these rows onto the rail's step.
*
* The ticket blamed `.cg-radio-row`. That was wrong on the mechanism and right on the naming:
* index.css's `.cg-radio-row` declares no font-size whatsoever (only display / align-items / gap /
* padding / border-radius / cursor, and a 15px input box), so it could not have been the source.
* The size was pure INHERITANCE, because `.cg-view-menu` sets no font-size either. The class is
* still wrong on a checkbox list, so the rows get their own name here and every layout property
* they used to borrow is restated below. Nothing else in the repo uses this class, so no other
* `.cg-radio-row` list is reached.
*
* Tokens only: `--lp-fs-2xs` is the scale step, never a literal.
*/
.cg-export-view-row {
display: flex;
align-items: center;
/* One step down from the radio row's 9px, onto the 4/8 rhythm: at the smaller step the old
gap left the box floating away from its own label. */
gap: 8px;
/* Vertical padding likewise tightens 6px to 4px so a 20-row list stays a list rather than a
column of buttons. Horizontal stays 8px, so the rows keep the same left edge as
`.cg-pop-title` and `.cg-pop-note` above them. */
padding: 4px 8px;
border-radius: var(--lp-r-md);
font-size: var(--lp-fs-2xs);
line-height: 1.45;
color: var(--cg-text);
cursor: pointer;
}
.cg-export-view-row:hover {
background: var(--lp-surface-2);
}
/* The 15px box is unchanged: it is the same control the rest of the app ships, and centring it
against a single line of the smaller step is what keeps it on the text's optical baseline. */
.cg-export-view-row input {
accent-color: var(--lp-blue-deep);
width: 15px;
height: 15px;
flex: 0 0 auto;
margin: 0;
cursor: pointer;
}
/* A View name is TENANT CONTENT inside a panel with a 260px ceiling, so it truncates rather than
wrapping the row to two lines. Same treatment `.cg-radio-row > span:not([class])` gave it. */
.cg-export-view-row > span {
flex: 1 1 auto;
min-width: 0;
overflow: hidden;
text-overflow: ellipsis;
white-space: nowrap;
}
/* WAVE 46 - T04. The data layer's create door now renders at every level and sits directly under
* the Back row, where the view layer's `.cg-create-new` sits under the shared band. That view-layer
* wrapper carries `margin-top: 8px` and `.cg-data-create` carried none, so the two doors would
* start on different rhythms once they became visible side by side across a drill-in. Same step,
* so the two layers read as one control in that row. */
/* ⛔ W47-T10 (repaired at /wave-validate, 2026-08-31): the PADDING had to come with the
margin. W47-T10 made the two doors' button markup identical and the wrappers still differed:
`.cg-create-new` carries `padding: 2px 2px 0` (index.css) and this one carried none, so the
control still stepped 2px on the walk between levels -- the exact "visual jump" the ticket's
done-when forbids. Lane B recorded it as unresolved because index.css is in no lane's fence. */
.cg-data-create {
margin-top: 8px;
padding: 2px 2px 0;
}
/* WAVE 46 - T06. The database row's "..." is a shell `.shell-dots`, not a `.cg-view-more`.
*
* It arrives through the `renderDatabaseActions` prop (Shell.tsx fills it with the shell's own
* `RowMenu`), so the button lands as a direct child of `.cg-fold-head` inside the views rail.
* Every rule in `shell/navExtras.css` is scoped to `.shell-nav-row > .shell-dots` or
* `.shell-nav-folder > .shell-dots`, and neither parent exists here, so NOT ONE of them matched
* and the button fell back to native UA chrome: a 1.78px outset black border over rgb(240,240,240)
* at 29.6x22.2. That is the owner's "big square outline" and the tinted fill DESIGN.md section 4
* forbids. The fix restores the quiet-button treatment the shell already gives this control in its
* own nav, sized to `.cg-view-more`'s 28x28 box so the database row's control and the view row's
* control are the same shape on the same baseline.
*
* ⛔ THE `button` TAG IN THE SELECTOR IS LOAD-BEARING, NOT DECORATION. `.shell-nav-row >
* .shell-dots` is (0,2,0); a plain `.cg-fold-head > .shell-dots` is also (0,2,0) and would only
* TIE, leaving the winner to whichever sheet the bundler emits last, which no lane controls and
* which can flip between builds. The element qualifier makes this (0,2,1), so it wins outright.
* Do not "simplify" it back into a coin flip.
*
* VISIBILITY: always visible, deliberately. `.cg-view-more` ships `opacity: 0` and is revealed by
* `.cg-view-row:hover`, but `index.css` already carries the folder-head exception
* (`.cg-fold-head .cg-view-more { opacity: 1 }`) because a fold head is not a view row and nothing
* would ever reveal it. The database rows ARE `.cg-fold-head`, so following that precedent is what
* "exactly the same as the view rows' control" means here. It also protects against the shell rule
* gaining rail reach later and painting this button at zero opacity.
*/
.cg-fold-head > button.shell-dots {
flex: 0 0 28px;
width: 28px;
height: 28px;
padding: 0;
margin: 0;
border: 0;
border-radius: var(--lp-r-sm);
background: transparent;
font: inherit;
/* `.cg-view-more` declares `color: var(--cg-muted)`, which resolves to the same `--lp-muted` the
* shell gives this button. Named rather than inherited so the two controls cannot drift. */
color: var(--cg-muted);
display: grid;
place-items: center;
cursor: pointer;
opacity: 1;
}
.cg-fold-head > button.shell-dots:hover {
background: var(--lp-wash);
color: var(--lp-ink);
}
.cg-fold-head > button.shell-dots:focus-visible {
outline: 2px solid var(--lp-blue-deep);
outline-offset: 1px;
}
/* WAVE 46 - T08 (owner instruction 26). The rail's history row: back, forward and the folder
* breadcrumb, seated directly under "Minimize views" and above "+ Create new...".
*
* Only the ROW is styled here. The control shapes already exist in index.css
* (`.cg-path-history-button`, `.cg-path-segment`, `.cg-path-separator`), and drawing a second set
* beside them is how one surface ends up with two button shapes. This sheet loads after index.css
* (contract C6), so the seating below wins the equal-specificity fight it needs to win.
*/
.cg-view-path {
margin: 6px 0 2px;
border-bottom: 1px solid var(--lp-line);
}
/* One height and one baseline across back, forward and every crumb. */
.cg-segmented-path {
align-items: center;
min-height: 30px;
}
/* A long path scrolls inside the row; it never wraps the rail into a second line. */
.cg-segmented-path .cg-path-segments {
gap: 1px;
flex-wrap: nowrap;
}
.cg-path-separator {
padding: 0 1px;
user-select: none;
}
/* The current segment is where you are, so it is inert. It must still read as text, not as a
* greyed-out control: `aria-current` already gives it the filled, darker treatment in index.css,
* and this only removes the pointer. */
.cg-path-segment:disabled {
cursor: default;
opacity: 1;
}
.cg-path-segment,
.cg-path-history-button {
transition: background 140ms ease-out, color 140ms ease-out, opacity 140ms ease-out;
}
@media (prefers-reduced-motion: reduce) {
.cg-path-segment,
.cg-path-history-button { transition: none; }
}