/* wave 51 -- lane A (the Data module client and the record view). Pre-created at the wave base with its @import in index.css so no lane edits index.css (a shared file is a merge collision). Tokens only: var(--lp-*), var(--cg-z-*); no literal font-size (verify_ui goes RED), no hex, no text-transform: uppercase (DESIGN.md section 2). */ /* ⭐⭐ W51-T03 / R6 + C8 — the one-line body of a grid confirm dialog. ⛔ ONE RULE, NOT A COMPONENT. `.lp-dialog-body` in kit.css already owns the body's padding, scale and rhythm; all this adds is the paragraph reset a
needs inside it, so the delete count and the record note sit on the same baseline as `ViewDeleteDisclosure`'s facts line. ⚠ GLOBAL BY NECESSITY, like the kit's own rules: `ConfirmDialog` renders through `BodyPortal`, so it is a direct child of
and every descendant-scoped selector is dead to it ([[a-portal-overlay-carries-its-own-surface]]). This file is imported from index.css. ⚠ NO font-size here. The scale comes from `.lp-dialog-body`; a literal one reds verify_ui. */ .cg-dialog-line { margin: 0; color: var(--lp-muted); } /* ═══════════════════════════════════════════════════════════════════════════════════════════ ⭐⭐ W51-T06 (R2 / R5, contract C6) — THE RECORD VIEW'S RELATED TABS AND THE PINNED CHIP. ═══════════════════════════════════════════════════════════════════════════════════════════ */ /* ⭐⭐ CLAUSE 5 — THE PIN IS THE FIRST CHIP **IN** THE FILTER BAR, NOT A SECOND ROW ABOVE IT. ⛔⛔ `display: contents` IS THE WHOLE OF THE BLAST-RADIUS CONTROL, and it is deliberate rather than exotic. `.cg-toolbar` is `container-type: inline-size` with a family of `> child` and `:has(> …)` rules across four wave stylesheets, and it is a direct flex child of `.cg-main` (a column). A wrapper that laid out would change that for EVERY grid in the product to serve one mode. `display: contents` removes the wrapper from layout entirely, so on every surface that is not a related tab the toolbar stays exactly the direct flex child it has always been: same container query, same `:has()` matches, same order integers. ⚠ The `:has()` test is on the CHIP, not on a modifier class, so the two can never disagree about whether the bar is pinned: the rule is true exactly when the chip is in the DOM. */ .cg-relpin-bar { display: contents; } .cg-relpin-bar:has(> .cg-relpin-chip) { display: flex; align-items: center; flex: 0 0 auto; min-width: 0; gap: 8px; padding-left: 10px; background: var(--lp-surface); border-bottom: 1px solid var(--lp-line); } /* The strip's hairline moves to the wrapper so the chip and the controls sit under ONE line rather than the chip floating beside a bordered box. `min-width: 0` is not optional: without it the toolbar's `container-type: inline-size` cannot shrink below its content and the strip overflows the panel instead of collapsing to icons the way it is designed to. */ .cg-relpin-bar:has(> .cg-relpin-chip) > .cg-toolbar { flex: 1 1 auto; min-width: 0; border-bottom: 0; padding-left: 4px; } /* ⭐ A LOCKED VIEW'S CHIP: a mark, a sentence, and NO REMOVE CONTROL. It is a and not a