loopable / web /src /styles /wave46 /map-panels.css
fsanyoto's picture
Deploy AIOS web (React glide grid + FastAPI slice)
e9a4c3e verified
Raw History Blame Contribute Delete
28.6 kB
/* Wave 46 β€” map panel chrome (W46-T17: the Zone drawing arming button).
β›” THIS SHEET IS IMPORTED FROM `customer-grid/MapView.tsx`, NOT FROM index.css, AND THAT IS
LOAD-BEARING. index.css @imports the wave-41/42 sheets at its TOP, so an @imported rule loses
every equal-specificity fight with the thousands of rules below it. A sheet imported from a
component lands AFTER index.css in the bundle and therefore wins its ties, which is the only
way `.cg-zone-draw-btn` can restate anything `.cg-link-btn` already sets.
Tokens only: no literal font sizes, no inline hex. */
/* The arming button. It was a bare word with no icon and no state, so it read as a sentence
fragment rather than a control, and nothing on screen said whether drawing was on.
Same 28px row and same radius as every other quiet control in the panel; the icon sits inside
the label rather than beside it so the pair moves as one target. */
.cg-zone-draw-btn {
display: inline-flex;
align-items: center;
justify-content: center;
gap: 6px;
flex: 0 0 auto;
padding: 0 10px;
border-color: var(--lp-line);
background: var(--lp-surface);
color: var(--lp-ink);
font: inherit;
font-size: var(--lp-fs-xs);
}
/* ARMED is a real state, not a label change: the map is a drawing surface for as long as this
is lit, and the user needs to know that before wondering why a click stopped opening records. */
.cg-zone-draw-btn.is-armed {
border-color: var(--lp-primary);
background: var(--lp-blue-tint);
/* Text takes `--lp-primary`, not `--lp-blue-deep`: that token is documented at 3.29:1 and is
for borders and focus rings, so a label wearing it would be under the text floor. */
color: var(--lp-primary);
}
.cg-zone-draw-btn:hover {
background: var(--lp-blue-tint);
}
.cg-zone-draw-btn:focus-visible {
outline: 2px solid var(--lp-primary);
outline-offset: 2px;
}
/* The glyph tracks the label's colour through `currentColor`, so the armed state recolours both
with one rule. `flex: 0 0 auto` keeps it square when the label wraps its container. */
.cg-zone-draw-ico {
width: 14px;
height: 14px;
flex: 0 0 auto;
}
/* The in-progress outline never takes a pointer event: it is drawn LAST in the SVG, on top of
the pins, so without this it would swallow the very clicks that extend it. */
.cg-zone-keyboard-draft {
pointer-events: none;
}
/* ── W46-T26: a route stop is a NAME with a number beside it ───────────────────────────────
The list printed "Stop 1", "Stop 2" β€” an ordinal is not an identity, and a driver reading the
panel could not tell one call from the next. The name is now the content and the number is
furniture, which DESIGN.md Β§2 makes a weight decision rather than a size one: the ordinal drops
to the micro-label scale and the muted ink, the name keeps the button's own link colour.
⚠ The number lives INSIDE the button, not beside it. `.cg-w44-route-stops li` in map.css is a
two-column grid (the open button, then the reorder controls); a third child would break the row.
⚠ No `overflow` or `max-height` on the list itself: the Route aside owns the panel's one
vertical scroller and a second one inside it is the defect W43C-T09 exists to prevent. */
.cg-w44-route-stop-open {
display: flex;
align-items: baseline;
gap: 8px;
min-width: 0;
/* ⭐ W47-T04: the button GROWS to fill the line and never wraps. `width: 100%` was the other
half of the wrapping defect - at 100 percent of a flex row it pushed the action cluster out
of the line entirely.
β›” THE BASIS IS 0, NOT `auto`, AND THAT IS THE WHOLE FIX. With `flex-basis: auto` the button
asks for its CONTENT width, and because the row may wrap, the browser grants it and pushes
the action cluster onto a second line instead of shrinking the button. A basis of 0 makes the
button claim only the space left after the grip and the controls, which is what finally lets
the name span's own ellipsis engage. Truncation still lives on the name, so the ordinal is
never the part that is clipped. */
flex: 1 1 0;
overflow: hidden;
text-overflow: clip;
white-space: nowrap;
}
/* The name is the only part that may shrink, and it must be allowed to hit zero for the
ellipsis to appear at all. */
.cg-w46-stop-name {
flex: 1 1 0;
}
/* The per-stop validation message is the ONE thing allowed a second line. */
.cg-w44-route-order-error {
flex: 1 0 100%;
}
/* `tabular-nums` plus the floor width keeps every name starting on the same x once the route
passes nine stops, so the column of names reads as a column. */
/* ⭐ OWNER 2026-08-31 item 3 - THE STOP ORDINAL IS A FILLED PURPLE DISC WITH WHITE INK.
Owner: *"the details for each stops under each route should only have the number 1, 2, 3 etc.
put it inside a purple circle and the font be colored white."* Confirmed in the grill that this
is the OPENED Route panel's stop list; the rail itself carries no numbering at all.
⚠ IT IS A FIXED SQUARE, NOT A PADDED ONE. A disc sized by its own text is an oval at "10" and
a circle at "1", and a route of a dozen stops shows both on one screen. 18px holds two digits
at this size; three digits ellipsise rather than reflowing the row, which is the same trade the
name beside it already makes. */
.cg-w46-stop-index {
flex: 0 0 auto;
display: inline-grid;
place-items: center;
width: 18px;
height: 18px;
border-radius: 50%;
background: var(--lp-primary);
color: var(--cg-white);
font-size: var(--lp-fs-3xs);
font-weight: 600;
font-variant-numeric: tabular-nums;
line-height: 1;
overflow: hidden;
}
.cg-w46-stop-name {
min-width: 0;
overflow: hidden;
text-overflow: ellipsis;
white-space: nowrap;
}
/* ── W46-T28: a Zone you can actually see, and vertices you can grab ───────────────────────
Owner instruction 16: *"the zone color is not strong enough its too transparent, i can't se
eshit."* The value is a TOKEN in both seams it has, per DESIGN.md section 5.
β›” THE `index.css :root` SEAM IS DELIBERATELY NOT USED. Contract C6: no lane edits
`aios-web/web/src/index.css`. The custom property is declared here instead, and its TS twin is
`LP_ZONE_FILL_OPACITY` in `customer-grid/theme.ts`. Two seams, one number: change both.
β›” AND THE SELECTOR CARRIES A SECOND CLASS ON PURPOSE. The rule being raised is
`.cg-map-zone { fill-opacity: 0.18 }` in `styles/wave45/data-applications.css`, which
`CustomerGrid.tsx:114` imports BEFORE it imports MapView at :141 β€” so today this sheet does
land later and would win the tie on order alone. That is a fact about one importer, not about
the rule: a second importer of MapView, or a reordered import line, silently flips it back and
every gate stays green ([[a-lane-stylesheet-cannot-override-index-css]]). `.cg-map-svg
.cg-map-zone` wins on SPECIFICITY (0,2,0 against 0,1,0), which no import order can undo. */
/* β›” 0.1 -> 0.8, owner correction 2026-08-31: *"i don't mean 10% I mean to say 80% opacity"*.
⭐ This is the FALLBACK now. `MapView.tsx` sets `--lp-zone-fill` inline on `.cg-mapview` from
its `zoneFillOpacity` state, so this value is what paints before that state mounts and after a
reader clears their stored preference. Both seams still hold one number (C1) -- and now they
cannot drift, because the component is the single writer of both. */
:root {
--lp-zone-fill: 0.8;
}
/* ⭐ W47-T01 (owner instruction 2). The FILL drops to 0.1 so the record dots read through a
Zone, and the legibility that buys back is paid at the BOUNDARY: `stroke-opacity` goes to a
flat 1 here, and the stroke WEIGHT is raised in the TS seam as `LP_ZONE_STROKE_WIDTH`.
β›” THE WEIGHT CANNOT LIVE IN THIS FILE. Zone outlines render inside `<g transform={tf}>`, so a
CSS `stroke-width` would be in user units and would thicken as the camera zooms; `hair()` in
`MapView.tsx` divides by the zoom to stop exactly that. A rule here WOULD win over the
presentation attribute, which is what makes writing one a silent regression rather than a
no-op. */
.cg-map-svg .cg-map-zone {
fill-opacity: var(--lp-zone-fill);
stroke-opacity: 1;
}
/* A vertex handle. It sits INSIDE the camera transform with the boundary it belongs to, and
deliberately OUTSIDE `.cg-zone-keyboard-draft`, which is `pointer-events: none` β€” a dot in
there could never be grabbed. `cursor: grab` is the whole affordance: nothing else on the map
says "this one point moves" as against the boundary drag, which moves all of them.
⚠ `vector-effect: non-scaling-stroke` is NOT used here: `verify_map.py`'s
`map-css-no-non-scaling-stroke` leg reds on it, and the ring below is pre-divided by the zoom
in the component the same way every other line on this map is. */
.cg-map-zone-vertex {
cursor: grab;
}
.cg-map-zone-vertex:active {
cursor: grabbing;
}
.cg-map-zone-vertex:focus-visible {
outline: none;
stroke: var(--lp-primary);
}
/* The draft controls sit on one row so "Finish shape" and "Stop drawing" read as the pair of
endings they are, rather than one control and one afterthought. */
.cg-zone-draw-actions {
display: flex;
flex-wrap: wrap;
gap: 6px;
align-items: center;
}
/* ── W47-T03: a finished Zone that has not been saved is a STATE, and it now looks like one ──
Owner instruction 20: *"When I click 'Finish zone' under the Zone navigation, the zone just
disappear. Only when I save the zone does it actually reappear. This is really bad UI, i was
really confused whether I have made the zone or not."* The boundary was reaching
`drawnZoneGeometry` and no render path at all, so finishing a shape deleted it from the screen.
β›” THE FILL IS HALF `--lp-zone-fill` AND THAT RATIO IS THE POINT. "Lighter than a saved Zone"
has to survive somebody retuning the saved value β€” which already happened once, when
instruction 16's *"i can't se eshit"* took `--lp-zone-fill` from 0.18 to 0.4. A second hand
picked number would have silently stopped being lighter that day, and W47-T01 then retuned it
AGAIN in the other direction (0.4 -> 0.1 for instruction 2), which this ratio absorbed. Declared here rather than in
`index.css :root` for the same reason its twin above is: contract C6, no lane edits index.css.
β›” NO `stroke-dasharray` HERE, ON PURPOSE. The dash is a component attribute driven by
`hair()`, because this group renders inside the camera transform where a user-unit dash grows
with the zoom, and the usual cure β€” `vector-effect: non-scaling-stroke` β€” is exactly what
`verify_map.py`'s `map-css-no-non-scaling-stroke` leg reds the build over. */
/* ⭐ STILL EXACTLY HALF, and this is the third retune the ratio has absorbed: 0.18 -> 0.4
(instruction 16), 0.4 -> 0.1 (W47-T01), and now 0.1 -> 0.8 (the owner's correction). A
hand-picked number would have stopped being "lighter than a saved Zone" at every one of them.
`MapView.tsx` computes the inline override as `zoneFillOpacity / 2`, so the ratio survives the
slider too. */
:root {
--lp-zone-fill-unsaved: 0.4;
}
.cg-map-svg .cg-map-zone-unsaved {
fill-opacity: var(--lp-zone-fill-unsaved);
/* A preview of a boundary is never a target. The pins, the saved Zones and the map beneath it
keep every click, the same way `.cg-zone-keyboard-draft` gives back the clicks that built it. */
pointer-events: none;
/* It ARRIVES rather than blinking into existence: 160ms of opacity reads as the shape settling
where the user just drew it. Opacity only, inside DESIGN.md section 4's 100-200ms ease-out
window, and off entirely for anyone who has asked for less motion. */
animation: cg-zone-unsaved-in 160ms ease-out;
}
@keyframes cg-zone-unsaved-in {
from { opacity: 0; }
to { opacity: 1; }
}
@media (prefers-reduced-motion: reduce) {
.cg-map-svg .cg-map-zone-unsaved {
animation: none;
}
}
/* The sentence under the pair. A dashed outline says "provisional" to a designer; it says nothing
to somebody who has drawn one Zone in their life, and it says nothing at all to a screen reader
over an `aria-hidden` group. So the state is also written down, in the panel, as text. */
.cg-zone-unsaved-note {
color: var(--lp-muted);
font-size: var(--lp-fs-3xs);
line-height: 1.4;
}
/* == W46-T29: the map toolbar wears the toolbar's own chrome, and its panels open right ======
Owner instruction 29: *"The formatting for Routes and zones / Location / No size should be
extremely similar to Filter/sort/group etc. With the coloring when its on etc. and icons, and
no outline for the button. ALSO ... the navigation for routes and zones etc should popup on
the right side of the screen not left as it is now."*
R8 fixes the reading: Filter/sort/group are the STYLE REFERENCE and do not move; the positional
change is the panel, which anchors to the right edge of the page.
THE REFERENCE IS `.cg-tb-btn` (index.css:1508) AND IT IS COPIED, NOT APPROXIMATED. Three
declared values carry the whole "no outline for the button" ask:
border 1px solid transparent (a box that reserves its metrics and paints nothing)
background transparent (no white fill against the toolbar ground)
font-size var(--lp-fs-xs) (declared, never inherited: index.css:1508 records why)
plus height 30px, padding 0 9px, gap 6px, radius var(--lp-r-md), line-height 1.
TWO DELIBERATE DEVIATIONS, AND THEY ARE OUTSIDE THE PARITY CLAUSE (border, background,
font-size). `.cg-tb-btn svg` is a LITERAL `#5a5a66` and `.cg-tb-btn:hover` a literal `#f0f2f5`;
`verify_icons.semantic_chip_tokens()` reds the build over one literal hex in a new sheet, so
those two take `var(--lp-muted)` (#6b7280) and `var(--lp-surface-2)` (#f7f7f6). β›” Do not
"restore parity" by pasting the hexes back: the gate is the reason, not an oversight.
THE ACTIVE HUE IS BLUE, AND IT IS AN EXISTING PAIR RATHER THAN A NEW ONE. `.cg-tb-btn.is-active`
itself is `var(--lp-blue-tint)` + `var(--lp-ink)`; the route toggle's own hover/open state was
already blue-tint; `.cg-zone-draw-btn.is-armed` above uses it. Green, yellow and purple are
RESERVED semantics (filter, sort, group β€” index.css:1562-1581) and borrowing one here would
say "this narrows the table", which it does not. */
/* Routes and Zones. Replaces index.css:5027's `border: 1px solid var(--lp-line)` and
`background: #ffffff` β€” the outline and the fill the owner is pointing at. `.cg-map-settings >`
takes this to 0,2,0 so it outranks the original on SPECIFICITY, not merely on sheet order. */
.cg-map-settings > .cg-map-route-toggle,
.cg-map-settings > .cg-mode-field {
box-sizing: border-box;
display: inline-flex;
align-items: center;
gap: 6px;
height: 30px;
padding: 0 9px;
border: 1px solid transparent;
border-radius: var(--lp-r-md);
background: transparent;
color: var(--lp-ink);
font: inherit;
font-size: var(--lp-fs-xs);
line-height: 1;
cursor: pointer;
white-space: nowrap;
transition: background 0.12s ease, color 0.12s ease;
}
.cg-map-settings > .cg-map-route-toggle svg,
.cg-map-settings > .cg-mode-field svg {
color: var(--lp-muted);
flex: 0 0 auto;
}
/* 0,3,0 and 0,4,0: `.cg-fsel:hover:not(:disabled)` (index.css:754) paints a blue border, which
against a transparent 1px box would put the outline back on hover alone. */
.cg-map-settings > .cg-map-route-toggle:hover,
.cg-map-settings > .cg-mode-field:hover:not(:disabled) {
border-color: transparent;
background: var(--lp-surface-2);
}
/* ON. The route toggle owns `is-open`; the two field buttons have NO state class to hang this on
(`.cg-fsel.is-empty` / `.is-missing` are both unreachable here, because `viewModes.tsx` passes
`value = field?.key ?? ""` and its own list carries a `""`-key row, so `current` always
resolves), so the open state is read off `aria-expanded`, which is the same fact `is-open`
records for the sibling. */
.cg-map-settings > .cg-map-route-toggle.is-open,
.cg-map-settings > .cg-mode-field[aria-expanded="true"] {
border-color: transparent;
background: var(--lp-blue-tint);
color: var(--lp-ink);
}
.cg-map-settings > .cg-map-route-toggle.is-open svg,
.cg-map-settings > .cg-mode-field[aria-expanded="true"] svg {
color: var(--lp-ink);
}
/* `.cg-select:focus` (index.css:2453) answers focus with a border colour and a 3px glow; the
reference answers it with an outline on focus-visible only, so the glow is retired here. */
.cg-map-settings > .cg-mode-field:focus {
border-color: transparent;
box-shadow: none;
}
.cg-map-settings > .cg-map-route-toggle:focus-visible,
.cg-map-settings > .cg-mode-field:focus-visible {
outline: 2px solid var(--lp-blue-deep);
outline-offset: 1px;
}
/* ── The panels open on the RIGHT ──────────────────────────────────────────────────────────
⚠ WHAT WAS ACTUALLY LEFT, MEASURED BEFORE THE EDIT. Three of the four asides in MapView carry
`.cg-route-nav-panel`, and `styles/wave45/data-applications.css:15` already gives those
`inset: 0 0 0 auto` at 0,4,0 β€” which beats `index.css:5048`'s `.cg-route-popover { left: 12px }`
at 0,1,0 whatever the sheet order. So the Routes index, the Zone chooser and the Zone editor
were right-flush already; the one still on the left was the BARE `.cg-route-popover`, the route
selection notice (MapView.tsx:3398).
It is restated here anyway, and that is the point: this sheet is imported from `MapView.tsx`
and therefore lands LAST, so the contract "these panels are right-anchored" is now written
where it wins its ties, instead of resting on one import line in `CustomerGrid.tsx`
([[a-lane-stylesheet-cannot-override-index-css]]).
⚠ NEITHER FORM CAN CLIP, AT 1024px OR ANYWHERE ELSE, and the reason is arithmetic rather than
a breakpoint. The bare panel is `width: min(360px, calc(100% - 24px))` against `right: 12px`,
so its left edge sits at `100% - width - 12px`, which is >= 12px for every container width; the
nav panels are `min(360px, 100%)` against `right: 0`, so theirs is >= 0. The width is already
bounded by the container MINUS the offset, which is what makes the offset safe.
⚠ And `@media (max-width: 1000px)` in `data-applications.css:117` (which narrows the nav panel
to `min(336px, calc(100% - 48px))`) does NOT fire at a 1024px window β€” it starts at 1000. */
.cg-mapview > .cg-map-bar > .cg-route-popover {
right: 12px;
left: auto;
}
/* Flush to the frame edge, not inset: these are the full-height drawers wave 45 shaped, and
their `border-left` is the seam that reads as an edge. Same value wave45 declares, restated
at 0,4,0 in the later sheet so an import reorder cannot quietly send them back left. */
.cg-mapview > .cg-map-bar > .cg-route-popover.cg-route-nav-panel {
right: 0;
left: auto;
}
/* ═══════ W47-T01/T04 β€” THE PANEL WIDTH, AND WHY IT IS DECLARED HERE AT 0,4,1 ═══════════════
Owner instruction 4: *"maybe we can increase the width of the whole route/zone navigation."*
β›” THE TICKET'S NAMED SEAM WAS ALREADY DEAD. `styles/wave45/data-applications.css` declares
`width: min(440px, 100%)` for this panel, and it does NOT win: `styles/wave42/route-nav.css`
declares `width: min(380px, 100%)` on the IDENTICAL selector and, being a later sheet in the
bundle (byte 54691 against 48802 in the built CSS), takes the tie on source order. Measured,
not assumed: the live panel computed to exactly 380px while the wave45 sheet said 440.
β›” SO THIS RULE REPEATS `.cg-route-popover` TO REACH 0,4,1 AND WIN ON SPECIFICITY INSTEAD OF
ORDER, the same defence `.cg-map-svg .cg-map-zone` uses against its own stale twin. An import
reorder cannot undo it.
⚠ THIS IS A PATCH OVER A DUPLICATE, NOT A FIX OF ONE. `styles/wave42/route-nav.css` is in NO
lane's FILE OWNERSHIP fence this wave, so its 380px cannot be deleted from here. Three sheets
now hold an opinion about one width. Collapsing them to one is integrator work, and it is
recorded in lanes/A/LANE_CONTEXT.md rather than left for somebody to rediscover. */
.cg-mapview > .cg-map-bar > .cg-route-popover.cg-route-popover.cg-route-nav-panel {
width: min(440px, 100%);
}
@media (max-width: 1000px) {
.cg-mapview > .cg-map-bar > .cg-route-popover.cg-route-popover.cg-route-nav-panel {
width: min(420px, calc(100% - 48px));
}
}
/* ═══════════════════ W46-T19 / R9 / C2 β€” the route timer and the drag grip ═══════════════════
THE TIMER SITS ABOVE THE STOPS IT IS ABOUT, which is what makes it readable as a property of
the whole drive rather than of the first stop. Two tones, and the difference between them is
the whole of C2's client half: a road answer is ink, an arithmetic one is muted and carries
the word "estimated" in its own label. Nothing here invents a colour or a size; the muted
token is the same one the rest of this panel's secondary copy already wears.
⚠ THE NUMBER MUST RENDER AT POINTER SPEED. Every rule below is paint only: no layout property
animates, and the drag state is one opacity change over 120ms, so a stop being moved across a
list of a hundred never waits on a style recalculation, let alone on a request. */
.cg-w46-route-timer {
display: flex;
flex-direction: column;
gap: 4px;
margin: 0 0 10px;
padding: 8px 10px;
border: 1px solid var(--lp-line);
border-radius: 8px;
background: var(--lp-surface);
}
.cg-w46-timer-head {
display: flex;
align-items: baseline;
gap: 8px;
flex-wrap: wrap;
}
/* The settled figure: the number a day is planned from, so it takes the page's own ink. */
.cg-w46-timer-time {
color: var(--lp-ink);
font-size: var(--lp-fs-lg);
font-weight: 600;
font-variant-numeric: tabular-nums;
}
/* The estimate. Muted is the ONLY signal that separates the two, so it is stated here once and
the label beside it says "estimated" in words for anyone who cannot see the difference. */
.cg-w46-timer-time.is-estimated {
color: var(--lp-muted);
font-weight: 500;
}
.cg-w46-timer-caption {
color: var(--lp-muted);
font-size: var(--lp-fs-2xs);
}
.cg-w46-timer-saving {
display: flex;
align-items: center;
gap: 8px;
flex-wrap: wrap;
}
.cg-w46-timer-saving > p,
.cg-w46-timer-note,
.cg-w46-timer-caveat,
.cg-w46-timer-error {
margin: 0;
font-size: var(--lp-fs-2xs);
line-height: 1.4;
}
.cg-w46-timer-saving > p {
color: var(--lp-ink);
}
/* A caveat and a cost are both things the reader has to take on board, so neither is allowed to
fade into furniture: muted, but at body weight rather than as a caption aside. */
.cg-w46-timer-note,
.cg-w46-timer-caveat {
color: var(--lp-muted);
}
.cg-w46-timer-error {
color: var(--lp-red-deep);
}
.cg-w46-timer-apply {
flex: 0 0 auto;
appearance: none;
border: 1px solid var(--lp-primary);
border-radius: 6px;
padding: 2px 10px;
background: var(--lp-blue-tint);
color: var(--lp-primary);
font: inherit;
font-size: var(--lp-fs-2xs);
cursor: pointer;
transition: background 120ms ease-out;
}
.cg-w46-timer-apply:hover:not(:disabled) {
background: var(--lp-surface);
}
.cg-w46-timer-apply:focus-visible {
outline: 2px solid var(--lp-primary);
outline-offset: 2px;
}
.cg-w46-timer-apply:disabled {
opacity: 0.55;
cursor: default;
}
/* The grip. Pointer only, and it says so by never taking focus; the arrows beside it are the
keyboard's way through the same reorder. */
.cg-w46-stop-grip {
display: inline-flex;
align-items: center;
flex: 0 0 auto;
color: var(--lp-muted);
cursor: grab;
touch-action: none;
}
.cg-w46-stop-grip:active {
cursor: grabbing;
}
.cg-w46-stop-grip > svg {
width: 12px;
height: 16px;
fill: currentColor;
}
/* The stop under the pointer. Opacity only, so the list never reflows mid drag. */
.cg-w44-route-stops > li.cg-w46-stop-dragging {
opacity: 0.55;
transition: opacity 120ms ease-out;
}
/* ── W46-T23 / INSTRUCTION 19 β€” the Route's name is edited where it is READ. ─────────────
Rename used to live in the list row's "..." menu and again in a "Route name" box down in the
edit block. Both are gone; the title is the field. Resting state must still read as a title,
so the control beside it stays quiet until the row is hovered or the button is focused. */
.cg-w44-route-title {
display: flex;
align-items: center;
gap: 6px;
min-width: 0;
}
.cg-w46-route-name {
min-width: 0;
overflow: hidden;
text-overflow: ellipsis;
white-space: nowrap;
}
.cg-w46-route-rename {
border: 0;
background: transparent;
font: 500 var(--lp-fs-3xs)/1.4 Inter, system-ui, sans-serif;
color: var(--lp-muted);
flex: 0 0 auto;
padding: 2px 4px;
border-radius: var(--lp-r-md);
cursor: pointer;
opacity: 0.5;
transition: opacity 140ms ease-out, color 140ms ease-out;
}
.cg-w44-route-title:hover .cg-w46-route-rename,
.cg-w46-route-rename:focus-visible {
opacity: 1;
color: var(--lp-primary);
}
.cg-w46-route-rename[disabled] {
opacity: 0.4;
color: var(--lp-muted);
cursor: default;
}
/* Editing: the input takes the title's place, its two controls sit on the same line so the row
never grows taller than the title it replaced. */
.cg-w46-route-rename-edit {
display: flex;
align-items: center;
gap: 6px;
flex: 1 1 auto;
min-width: 0;
}
.cg-w46-route-rename-edit .cg-w46-route-rename {
opacity: 1;
}
.cg-w46-route-name-input {
flex: 1 1 auto;
min-width: 0;
}
/* ═══════════════ W47-T07 β€” THE TICKED ROUTES, AND THE CHECKBOX THAT TICKS THEM ═══════════════
Owner instruction 9: *"we also need a checkbox for us to be able to see each route all together
on the map ... Each route should have a different color that is onbrand."*
β›” NO `stroke` HERE, ON PURPOSE. Every overlaid route wears its OWN persisted colour, set as an
attribute from `route.color`, so a stroke declared in this file would flatten all of them to one
and quietly undo the whole ticket. Weight and joins only.
β›” AND NO `stroke-width` EITHER: the line renders inside the camera transform, where a CSS width
is in user units and thickens with the zoom. `hair()` in `MapView.tsx` owns that number. This is
the third time in one wave the same trap has come up - see the note on `LP_ZONE_STROKE_WIDTH`. */
.cg-map-svg .cg-map-route-overlay {
fill: none;
stroke-linecap: round;
stroke-linejoin: round;
stroke-opacity: 0.95;
}
/* The swatch is now inside a label with the checkbox, so the pair needs to sit on one baseline. */
.cg-w44-route-toggle {
display: inline-flex;
align-items: center;
gap: 6px;
cursor: pointer;
}
.cg-w44-route-toggle input {
margin: 0;
cursor: pointer;
}
/* ═══════ OWNER 2026-08-31 β€” THE ZONE FILL OPACITY DIAL ═══════════════════════════════════════
*"let's make the Zone opacity toggleable under the Zone configuration module"*, alongside the
correction that instruction 2's "10% opacity" meant EIGHTY. The control sits in the Zone
configuration panel beside Color, and `MapView.tsx` owns its value.
⚠ THE ROW IS A THREE-PART LABEL, so it needs its own shape: `.cg-map-zone-control` is a column
for a label over a single control, and this one carries a slider AND its reading. The reading is
`tabular-nums` and width-floored so the row does not jitter as the number crosses 9 -> 10 -> 100,
which is the kind of movement that reads as the panel being broken. */
.cg-map-zone-control:has(> .cg-zone-opacity-range) {
display: grid;
grid-template-columns: 1fr auto;
align-items: center;
gap: 4px 8px;
}
.cg-zone-opacity-range {
width: 100%;
min-width: 0;
accent-color: var(--lp-blue-solid);
cursor: pointer;
}
.cg-zone-opacity-range:focus-visible {
outline: 2px solid var(--lp-blue-deep);
outline-offset: 2px;
}
.cg-zone-opacity-read {
min-width: 4ch;
color: var(--lp-muted);
font-variant-numeric: tabular-nums;
text-align: right;
}