Download web/src/automation/automation.css from fsanyoto/loopable: direct link, hf CLI and curl.
- Browser
- Download file 22.5 kB
-
https://huggingface.co/spaces/fsanyoto/loopable/resolve/main/web/src/automation/automation.css
- Command line
-
hf download hf://spaces/fsanyoto/loopable/web/src/automation/automation.css
-
curl -L -o automation.css https://huggingface.co/spaces/fsanyoto/loopable/resolve/main/web/src/automation/automation.css
22.5 kB
| /* --------------------------------------------------------------------------- | |
| automation/automation.css β the Agent module's OWN stylesheet. | |
| ββ WAVE 34 Β· W34-T41 β THIS FILE IS NEW, AND ITS EXISTENCE IS THE POINT. | |
| Until today this module had NO scoped CSS at all: every `auto-*`, `autob-*` and `autox-*` rule | |
| lived in the shared global `src/index.css`, which the wave PRD assigns to session C. That made | |
| any new rule here a cross-fence ask, for styling nobody else can see β the PRD's own remedy is | |
| "put NEW rules in your own module stylesheet (`automation/*.css`)", and this is that file. | |
| β WHAT DOES NOT BELONG HERE: an edit to an existing `auto-*` rule. Those still live in | |
| `index.css` and are still C's. This file holds rules that did not exist before, so the two can | |
| never disagree about one selector. | |
| β EVERY COLOUR IS A TOKEN. No literal hex, for the reason the palette block in `index.css` | |
| records: a hand-copied brand value silently paints last wave's brand while a comment asserts | |
| parity. Light and dark both come free that way. | |
| --------------------------------------------------------------------------- */ | |
| /* ββ the Chat view (R17) ββββββββββββββββββββββββββββββββββββββββββββββββββββ */ | |
| /* Mirrors `.autox-flow`'s box so switching Canvas <-> Chat does not move the frame around it: | |
| same flex growth, same min-height:0 (without which a scrolling child of a flex parent grows | |
| the parent instead of scrolling), same scroll ownership. */ | |
| .autoc-chat { | |
| flex: 1 1 auto; | |
| min-width: 0; | |
| min-height: 0; | |
| display: flex; | |
| flex-direction: column; | |
| } | |
| .autoc-log { | |
| flex: 1 1 auto; | |
| min-height: 0; | |
| overflow-y: auto; | |
| padding: 20px 24px 12px; | |
| display: flex; | |
| flex-direction: column; | |
| gap: 14px; | |
| } | |
| /* β `.autoc-empty` STOOD HERE AND WAS DELETED WITH ITS ONLY USER (W36-T30, owner item 4). A rule | |
| whose class no longer appears in any .tsx is dead weight the next reader has to prove is dead, | |
| which is why the tombstone is cheaper than the rule. W36-T33's rebuilt empty state gets its own. */ | |
| .autoc-msg { | |
| max-width: 60ch; | |
| padding: 10px 14px; | |
| border-radius: var(--lp-r-md); | |
| font-size: var(--lp-fs-sm); | |
| line-height: 1.5; | |
| white-space: pre-wrap; | |
| overflow-wrap: anywhere; | |
| } | |
| .autoc-msg.is-you { | |
| align-self: flex-end; | |
| background: var(--lp-surface-2); | |
| color: var(--lp-ink); | |
| } | |
| .autoc-msg.is-agent { | |
| align-self: flex-start; | |
| border: 1px solid var(--lp-line); | |
| color: var(--lp-ink); | |
| } | |
| /* β A FAILED TURN IS A MESSAGE, NOT A TOAST. A toast is gone before a reader has finished the | |
| sentence, and this surface's failures are things you act on (rephrase, pick a database). | |
| β `--lp-red-deep` / `--lp-red-tint`, CHECKED AGAINST THE PALETTE, not typed from memory: the | |
| first draft of this rule used `--lp-danger` and `--lp-danger-line`, and NEITHER EXISTS. A ghost | |
| custom property does not fail loudly β it falls back or inherits β so the error message would | |
| have painted in ordinary ink and looked like an answer. Same defect T14 caught on | |
| `--lp-ink-muted` in the same wave; the palette is the only source worth trusting. */ | |
| .autoc-msg.is-error { | |
| align-self: flex-start; | |
| border: 1px solid var(--lp-red); | |
| background: var(--lp-red-tint); | |
| color: var(--lp-red-deep); | |
| } | |
| /* What the model asked for and the validator would not keep. β It renders as ORDINARY content, | |
| not as a warning ornament: R6's standing rule is that a limit must be REPORTED, and a report | |
| nobody reads because it looks like chrome is the same as no report. */ | |
| .autoc-dropped { | |
| align-self: flex-start; | |
| max-width: 60ch; | |
| margin: 0; | |
| padding: 8px 12px; | |
| border-left: 2px solid var(--lp-line); | |
| color: var(--lp-muted); | |
| font-size: var(--lp-fs-xs); | |
| line-height: 1.5; | |
| } | |
| .autoc-dropped ul { margin: 4px 0 0; padding-left: 18px; } | |
| /* ββ W36-T33 β THE COMPOSER IS THE ASSISTANT'S, IN THIS MODULE'S NAMES. | |
| Owner: *"Just as good as the Assistant module."* The done-when is a comparison, so these rules | |
| mirror `assistant/assistant.css`'s `.as-field` / `.as-prompt` / `.as-field-foot` / `.as-send` | |
| on the SAME TOKENS. Not `@extend`, not a shared class: `.as-*` belongs to the Assistant's | |
| stylesheet and reaching into it would make one surface's restyle silently repaint the other. | |
| β WHAT MUST NOT DRIFT is the pair of numbers that carry the shape β the 22px pill radius and | |
| the field's shadow β because those are what the eye compares. Both are matched BY VALUE from | |
| `.as-field`, and the shadow is a literal because THIS PRODUCT HAS NO SHADOW TOKEN: `index.css` | |
| records that finding in as many words beside `.autoc-bigedit`, where naming a shadow token that | |
| does not exist would have quietly rendered its own fallback while looking like a token was | |
| being honoured. | |
| β AND THAT SENTENCE USED TO NAME THE TOKEN, WHICH BROKE THE GATE THAT READS THIS FILE. R17's | |
| "every token the new stylesheet uses is DEFINED in the palette" scans the raw text, comments | |
| included, so quoting `var(--β¦)` in prose counts as USING it: the citation reddened the check | |
| [[prose-that-becomes-its-own-marker]]. Describe a token you are NOT using; never spell it. */ | |
| /* β NO HAIRLINE ON THE BAND ANY MORE. The card below has its own border, and a rule across the | |
| pane above it made two edges 12px apart β the "still so ugly" the owner reported is mostly | |
| this kind of doubling. What separates the composer from the transcript now is whitespace. */ | |
| .autoc-compose { | |
| flex: 0 0 auto; | |
| padding: 8px 24px 20px; | |
| } | |
| .autoc-field { | |
| /* ONE measure for the conversation and the empty state, so the composer does not change width | |
| when the first message lands. `.as-opening .as-composer` caps at the same 700px. */ | |
| max-width: 700px; | |
| margin: 0 auto; | |
| border: 1px solid var(--lp-line); | |
| border-radius: 22px; | |
| background: var(--lp-surface); | |
| padding: 10px 8px 8px 16px; | |
| box-shadow: 0 1px 2px rgba(20, 24, 40, 0.05); | |
| box-sizing: border-box; | |
| } | |
| .autoc-field:focus-within { border-color: var(--lp-blue-solid); } | |
| /* β `rows={1}` PLUS `max-height`, which is `.as-prompt`'s shape and not the two-row box that was | |
| here. A composer that starts tall claims space before anybody has typed; the Assistant's grows | |
| into the sentence instead. */ | |
| .autoc-input { | |
| display: block; | |
| width: 100%; | |
| max-height: 180px; | |
| border: 0; | |
| outline: none; | |
| padding: 0 8px 0 0; | |
| background: transparent; | |
| color: var(--lp-ink); | |
| font: inherit; | |
| font-size: var(--lp-fs-sm); | |
| line-height: var(--lp-lh); | |
| resize: none; | |
| box-sizing: border-box; | |
| } | |
| .autoc-input::placeholder { color: var(--lp-muted); } | |
| /* The row BELOW the input and INSIDE the card β the reference screenshot's arrangement, and the | |
| slot W36-T34's model toggle drops into beside the send. */ | |
| .autoc-foot { | |
| display: flex; | |
| align-items: center; | |
| gap: 12px; | |
| margin-top: 8px; | |
| } | |
| .autoc-send { | |
| flex: 0 0 auto; | |
| margin-left: auto; | |
| width: 30px; | |
| height: 30px; | |
| display: inline-flex; | |
| align-items: center; | |
| justify-content: center; | |
| border: 0; | |
| border-radius: 999px; | |
| background: var(--lp-ink); | |
| color: var(--lp-surface); | |
| cursor: pointer; | |
| } | |
| .autoc-send svg { | |
| fill: none; | |
| stroke: currentColor; | |
| stroke-width: 1.7; | |
| stroke-linecap: round; | |
| stroke-linejoin: round; | |
| } | |
| .autoc-send:disabled { background: var(--lp-surface-2); color: var(--lp-muted); cursor: default; } | |
| .autoc-send:focus-visible { outline: 2px solid var(--lp-blue-deep); outline-offset: 1px; } | |
| /* ββ the empty state (mirrors `.as-opening`) ββββββββββββββββββββββββββββββββ */ | |
| .autoc-opening { | |
| flex: 1 1 auto; | |
| min-height: 0; | |
| display: flex; | |
| flex-direction: column; | |
| align-items: center; | |
| justify-content: center; | |
| padding: 24px; | |
| box-sizing: border-box; | |
| text-align: center; | |
| } | |
| .autoc-opening-h { | |
| margin: 0 0 6px; | |
| color: var(--lp-ink); | |
| font-size: var(--lp-fs-lg); | |
| font-weight: 650; | |
| } | |
| .autoc-opening-p { | |
| max-width: 52ch; | |
| margin: 0 0 20px; | |
| color: var(--lp-muted); | |
| font-size: var(--lp-fs-sm); | |
| line-height: var(--lp-lh); | |
| } | |
| /* The composer is left-aligned inside a centred column, exactly as the Assistant's is: centred | |
| placeholder text in a wide field reads as a search box, not as somewhere to write a sentence. */ | |
| .autoc-opening .autoc-field { width: 100%; text-align: left; } | |
| /* The pending row. β It uses `.lp-spin`, the ONE loading mark app-wide (purple as of this wave's | |
| T24) β a second spinner vocabulary in a new surface is how an app stops having one. */ | |
| .autoc-pending { | |
| display: flex; | |
| align-items: center; | |
| gap: 8px; | |
| align-self: flex-start; | |
| color: var(--lp-muted); | |
| font-size: var(--lp-fs-sm); | |
| } | |
| /* The accept bar. It is deliberately NOT inside the transcript: accepting is an act on the | |
| AUTOMATION, not a reply in the conversation, and putting it in the log would make it scroll | |
| away from the thing it acts on. */ | |
| .autoc-accept { | |
| flex: 0 0 auto; | |
| display: flex; | |
| align-items: center; | |
| gap: 10px; | |
| padding: 10px 24px; | |
| border-top: 1px solid var(--lp-line); | |
| background: var(--lp-surface-2); | |
| font-size: var(--lp-fs-sm); | |
| } | |
| .autoc-accept-note { color: var(--lp-muted); margin-right: auto; } | |
| /* ββ the run log's note disclosure (R21 / W34-T45) ββββββββββββββββββββββββββ */ | |
| /* β WAVE 34 Β· W34-T45. `notes` is up to 300 chars x 25 entries per run and was rendered | |
| unconditionally over 20 runs; that is the "too wordy" the owner reported. It is still | |
| unconditional for a run that FAILED or hit a cap (R6: a limit must be REPORTED) and behind this | |
| disclosure otherwise. | |
| β The list INSIDE stays `.auto-run-notes`, which is C's existing rule in `index.css`. Only the | |
| wrapper is new, so the notes themselves cannot start looking different depending on which | |
| branch rendered them. */ | |
| .autor-notes { | |
| margin: 2px 0 0; | |
| } | |
| .autor-notes-toggle { | |
| cursor: pointer; | |
| color: var(--lp-muted); | |
| font-size: var(--lp-fs-2xs); | |
| /* The default triangle is the affordance; no custom marker, because a disclosure that does not | |
| look like one is how a person decides there is nothing behind it. */ | |
| list-style: revert; | |
| } | |
| .autor-notes-toggle:hover { color: var(--lp-ink); } | |
| .autor-notes-toggle:focus-visible { | |
| outline: 2px solid var(--lp-blue-deep); | |
| outline-offset: 1px; | |
| } | |
| /* ββ the parked statements batch (W35-T36 / owner ruling R10) βββββββββββββββ */ | |
| /* ββ "N STATEMENTS ARE READY", with the ONLY Send control in the product. | |
| It sits above `.auto-work`, in the banner band, because it is the one thing on this agent that | |
| needs a person β R10's whole shape is that the run assembles and PARKS, and somebody releases. | |
| β IT IS DELIBERATELY NOT A WARNING COLOUR. A parked batch is the system working as designed, and | |
| painting it amber would teach people to dismiss the panel that guards a real mail send. It is | |
| the blue tint every other "here is something to look at" surface uses. */ | |
| .auto-batch { | |
| flex: 0 0 auto; | |
| margin: 12px 24px 0; | |
| padding: 12px 14px; | |
| border: 1px solid var(--lp-blue); | |
| border-radius: var(--lp-r-md); | |
| background: var(--lp-blue-tint); | |
| font-size: var(--lp-fs-sm); | |
| } | |
| .auto-batch-head { | |
| display: flex; | |
| align-items: baseline; | |
| flex-wrap: wrap; | |
| gap: 4px 10px; | |
| } | |
| .auto-batch-count { | |
| font-weight: 650; | |
| color: var(--lp-ink); | |
| } | |
| .auto-batch-note { color: var(--lp-muted); } | |
| /* The guardrail line. Same size as a note, because it IS one: the data layer decides, this | |
| reports (R6's second sentence). */ | |
| .auto-batch-safe, | |
| .auto-batch-line { | |
| margin: 6px 0 0; | |
| color: var(--lp-muted); | |
| font-size: var(--lp-fs-xs); | |
| line-height: 1.5; | |
| max-width: 70ch; | |
| } | |
| /* Who is about to be emailed. β Bounded in the MARKUP at 8 rows with an "and N more" line rather | |
| than scrolled here: a 200-row list inside a banner pushes the work area off the screen, and the | |
| panel's job is to say who and how many, not to be the worklist. */ | |
| .auto-batch-list { | |
| margin: 8px 0 0; | |
| padding: 0; | |
| list-style: none; | |
| display: flex; | |
| flex-direction: column; | |
| gap: 2px; | |
| font-size: var(--lp-fs-xs); | |
| } | |
| .auto-batch-list li { | |
| display: flex; | |
| gap: 10px; | |
| align-items: baseline; | |
| } | |
| .auto-batch-cust { color: var(--lp-ink); } | |
| .auto-batch-to { color: var(--lp-muted); overflow-wrap: anywhere; } | |
| .auto-batch-more { color: var(--lp-muted); } | |
| .auto-batch-actions { | |
| margin-top: 10px; | |
| display: flex; | |
| gap: 8px; | |
| } | |
| /* ββ W36-T44 (D-316 + D-299): the statements step's config panel βββββββββββββ */ | |
| /* NEW rules only, in this module's own stylesheet. Every `auto-*` rule the panel reuses | |
| (`auto-field`, `auto-input`, `auto-hint`, `auto-note`, `auto-btn`) still lives in the shared | |
| `index.css` and is still another lane's, so nothing here redefines one. */ | |
| /* The two action rows (Preview, Send one test). A row rather than a bare button so the two read | |
| as the same kind of control at the same left edge as every field above them. */ | |
| .autox-stmt-row { | |
| display: flex; | |
| gap: 8px; | |
| margin: 0 0 14px; | |
| } | |
| .autox-stmt-shot { | |
| margin: 0 0 14px; | |
| border: 1px solid var(--lp-line); | |
| border-radius: var(--lp-r-md); | |
| padding: 10px 12px; | |
| background: var(--lp-surface-2); | |
| } | |
| .autox-stmt-shot .auto-hint { | |
| margin: 0 0 8px; | |
| overflow-wrap: anywhere; | |
| } | |
| /* β A FIXED HEIGHT, AND IT SCROLLS INSIDE ITSELF. A statement for a customer with forty open | |
| invoices is a long document, and a preview that grows to its content pushes the test-send | |
| control below it off the panel: the one thing somebody must reach after reading a preview. | |
| β AND THE LITERAL WHITE IS THE ONE DELIBERATE EXCEPTION TO THIS FILE'S "every colour is a | |
| token" RULE, booked here rather than left to read as an oversight. What is inside this frame is | |
| not our chrome, it is the EMAIL: `render_statement_html` hard-codes #1F4E78 headers, #e3e8ef | |
| rules and near-black body text against an assumed white page, and the recipient's mail client | |
| will paint it on white whatever this app's theme is. A surface token would go dark in dark mode | |
| and render the real mail's dark text on a dark ground, so the preview would stop showing what | |
| goes out at exactly the moment somebody is checking what goes out. */ | |
| .autox-stmt-frame { | |
| display: block; | |
| width: 100%; | |
| height: 260px; | |
| border: 1px solid var(--lp-line); | |
| border-radius: var(--lp-r-sm); | |
| background: #fff; | |
| } | |
| /* ββ W36-T31 (owner item 3, R7/R8, contract C4): the Harness tab βββββββββββββ */ | |
| /* NEW rules only. Everything shared (`auto-field`, `auto-input`, `auto-btn`, `auto-note`, | |
| `auto-hint`, `auto-paneltab*`) still lives in `index.css` and is still another lane's. */ | |
| .autoh-wrap { | |
| display: flex; | |
| flex-direction: column; | |
| gap: 4px; | |
| } | |
| .autoh-files { | |
| margin: 0 0 14px; | |
| padding: 0; | |
| list-style: none; | |
| display: flex; | |
| flex-direction: column; | |
| gap: 2px; | |
| } | |
| .autoh-file { | |
| display: flex; | |
| align-items: center; | |
| gap: 6px; | |
| border-radius: var(--lp-r-sm); | |
| } | |
| .autoh-file.is-on { background: var(--lp-blue-tint); } | |
| /* The row is a BUTTON, so the whole line opens the file. A path that is only clickable on its | |
| own glyph-width is a target people miss and then decide is not clickable at all. */ | |
| .autoh-open { | |
| flex: 1 1 auto; | |
| min-width: 0; | |
| display: flex; | |
| flex-direction: column; | |
| gap: 1px; | |
| padding: 5px 8px; | |
| border: 0; | |
| border-radius: var(--lp-r-sm); | |
| background: transparent; | |
| color: var(--lp-ink); | |
| font: inherit; | |
| text-align: left; | |
| cursor: pointer; | |
| } | |
| .autoh-open:hover:not(:disabled) { background: var(--lp-surface-2); } | |
| .autoh-open:focus-visible { outline: 2px solid var(--lp-blue-deep); outline-offset: -2px; } | |
| .autoh-open:disabled { cursor: default; } | |
| /* β `anywhere`, not `ellipsis`: a harness path is `skills/router.md`, and the half that | |
| identifies it is the END. Truncating from the right hides exactly the distinguishing part. */ | |
| .autoh-path { | |
| font-size: var(--lp-fs-sm); | |
| font-weight: 600; | |
| overflow-wrap: anywhere; | |
| } | |
| .autoh-meta { | |
| color: var(--lp-muted); | |
| font-size: var(--lp-fs-2xs); | |
| overflow-wrap: anywhere; | |
| } | |
| /* Quiet until reached for. Deleting a file is a real act (it takes the history with it), so it is | |
| present and honest rather than hidden, but it does not compete with opening one. */ | |
| .autoh-drop { | |
| flex: 0 0 auto; | |
| opacity: 0.55; | |
| } | |
| .autoh-file:hover .autoh-drop, | |
| .autoh-drop:focus-visible { opacity: 1; } | |
| .autoh-newrow { | |
| display: flex; | |
| gap: 6px; | |
| align-items: center; | |
| } | |
| /* Monospace, because a harness file is a router or a skill: its indentation carries meaning and a | |
| proportional font makes a misaligned block look aligned. | |
| β THE FACE COMES FROM `.auto-input.is-mono`, WHICH THE TEXTAREA ALSO CARRIES, and this rule sets | |
| no `font-family` at all. `index.css:12591` records why in as many words: there IS no `--lp-mono` | |
| token, six sites spell the stack out, and a seventh copy here would put the product's mono face | |
| in two places that can drift. `WebActionConfig` reaches for the same class. */ | |
| .autoh-body { | |
| font-size: var(--lp-fs-xs); | |
| line-height: 1.55; | |
| resize: vertical; | |
| } | |
| .autoh-actions { | |
| display: flex; | |
| gap: 8px; | |
| margin: 0 0 14px; | |
| } | |
| .autoh-history { | |
| margin: 0 0 8px; | |
| padding: 0; | |
| list-style: none; | |
| display: flex; | |
| flex-direction: column; | |
| gap: 1px; | |
| } | |
| .autoh-history li { border-radius: var(--lp-r-sm); } | |
| .autoh-history li.is-on { background: var(--lp-blue-tint); } | |
| .autoh-version { | |
| width: 100%; | |
| display: flex; | |
| gap: 8px; | |
| align-items: baseline; | |
| padding: 4px 8px; | |
| border: 0; | |
| border-radius: var(--lp-r-sm); | |
| background: transparent; | |
| color: var(--lp-ink); | |
| font: inherit; | |
| text-align: left; | |
| cursor: pointer; | |
| } | |
| .autoh-version:hover:not(:disabled) { background: var(--lp-surface-2); } | |
| .autoh-version:focus-visible { outline: 2px solid var(--lp-blue-deep); outline-offset: -2px; } | |
| .autoh-version:disabled { cursor: default; } | |
| .autoh-vnum { | |
| flex: 0 0 auto; | |
| font-size: var(--lp-fs-xs); | |
| font-weight: 650; | |
| } | |
| /* The unsaved-edit hold. A bordered block rather than a tint, because it is a QUESTION waiting on | |
| an answer and the two buttons under it are the answer; a tinted note reads as commentary. */ | |
| .autoh-hold { | |
| margin: 0 0 14px; | |
| padding: 10px 12px; | |
| border: 1px solid var(--lp-line); | |
| border-radius: var(--lp-r-md); | |
| background: var(--lp-surface-2); | |
| } | |
| .autoh-hold .auto-note { margin-top: 0; } | |
| /* ββ W36-T32 (owner item 3, R7): the right rail folds behind a "III" βββββββββ */ | |
| /* β THE FOLD SITS AT THE RAIL'S OWN LEFT EDGE, AND `flex-start` IS ONLY HALF OF WHY. | |
| W35-T11 put the left rails' fold at their left edge; this rail is on the RIGHT, so its left | |
| edge is the one facing the chat it widens. `.auto-panel-head` is `space-between` and lives in | |
| `index.css` (another lane's), so this wrapper is what keeps the fold and the tabs together | |
| instead of flung to the panel's two edges. | |
| ββ AND NOTHING IN HERE MAY EVER CARRY `margin-left: auto`. W35-T28's real finding was that a | |
| sibling's auto margin ate the free space BEFORE `justify-content` applied, so one control sat | |
| left on one database and right on another: one control, two positions, decided by data. */ | |
| .autod-head { | |
| flex: 1 1 auto; | |
| min-width: 0; | |
| display: flex; | |
| align-items: center; | |
| justify-content: flex-start; | |
| gap: 10px; | |
| } | |
| /* The collapsed rail. Same width token and the same idea as `.auto-rail.is-collapsed` on the | |
| left of this screen: folding a rail leaves a strip, never a gap, because the strip is where the | |
| way back lives. */ | |
| .autod-shut { | |
| flex: 0 0 auto; | |
| width: var(--lp-rail-min); | |
| display: flex; | |
| justify-content: center; | |
| padding: 14px 6px 0; | |
| border-left: 1px solid var(--lp-line); | |
| background: var(--lp-surface); | |
| } | |
| /* β THE FOLD, IN ONE PLACE. Every `.auto-panel` in the work area goes at once β Properties (a | |
| child of AutomationBuilder), Harness and Run history (children of AutomationDetail) β so a | |
| panel added later folds without being told to. `display: none` also removes them from the | |
| accessibility tree, which is the property `hidden` was giving us and the reason a `visibility` | |
| or `width: 0` treatment would be a regression a screen reader would meet and nobody would see. */ | |
| .autod-folded .auto-panel { display: none; } | |
| /* ββ W36-T34 (owner item 3, R4, contract C5): the model toggle βββββββββββββββ */ | |
| /* Mirrors `.as-pick` / `.as-pick-label` / `.as-pick-select`: text inside the field rather than a | |
| boxed control, which is what makes it read as part of the composer instead of a second form. | |
| A native `<select>` keeps the keyboard and screen-reader behaviour a hand-rolled popover would | |
| have to re-earn β the Assistant's own note, and the same reason applies here. */ | |
| .autoc-pick { | |
| display: inline-flex; | |
| align-items: center; | |
| gap: 5px; | |
| min-width: 0; | |
| } | |
| .autoc-pick-label { color: var(--lp-muted); font-size: var(--lp-fs-2xs); } | |
| .autoc-pick-select { | |
| max-width: 150px; | |
| border: 0; | |
| background: transparent; | |
| color: var(--lp-ink); | |
| font: inherit; | |
| font-size: var(--lp-fs-2xs); | |
| font-weight: 600; | |
| cursor: pointer; | |
| } | |
| .autoc-pick-select:disabled { cursor: default; color: var(--lp-muted); } | |
| /* ββ W36-T69 (owner item 8, R9): a config that is READ, never typed ββββββββββ */ | |
| /* β A DEFINITION LIST, NOT DISABLED INPUTS. A greyed `<input>` reads as a control somebody could | |
| enable, invites a click that does nothing, and is announced to a screen reader as a form field. | |
| R9 removes the TYPING, not the information, so this renders the values as what they are. */ | |
| .autox-ro { | |
| margin: 0 0 12px; | |
| display: flex; | |
| flex-direction: column; | |
| gap: 6px; | |
| } | |
| .autox-ro > div { | |
| display: flex; | |
| gap: 10px; | |
| align-items: baseline; | |
| } | |
| .autox-ro dt { | |
| flex: 0 0 auto; | |
| min-width: 84px; | |
| color: var(--lp-muted); | |
| font-size: var(--lp-fs-2xs); | |
| } | |
| .autox-ro dd { | |
| margin: 0; | |
| color: var(--lp-ink); | |
| font-size: var(--lp-fs-xs); | |
| overflow-wrap: anywhere; | |
| } | |
| /* The lock on the step card. Muted, and inline with the title rather than on a line of its own: | |
| every card in this column is exactly two lines, and a third on one of them is the ragged edge | |
| the owner reads as unfinished. */ | |
| .autox-card-lock { | |
| display: inline-flex; | |
| align-items: center; | |
| margin-left: 6px; | |
| color: var(--lp-muted); | |
| vertical-align: middle; | |
| } | |