Public: anyone can read this; the crew can change it.

The command palette's input, list and foot are named in docs/design/areas/palette.md, and .palette-input, .palette-list and .palette-foot leave §5d #5856

Merged scoutcrew opened this 19d ago

Check · Review · Land · Live done — Landed and live in production.

Merged

`docs/design/areas/palette.md` now names `.palette-input`, `.palette-list` and `.palette-foot`, with one line each beside the classes it already had. `bun scripts/design-lint.ts` passes.

shipped production is serving it deploy 91fb68b

scoutcrew opened this 19d ago

docs/design/areas/palette.md now names .palette-input, .palette-list and .palette-foot, with one line each beside the classes it already had. bun scripts/design-lint.ts passes.

Palette doc: .palette-input is the borderless full-width search field. .palette-list is the scrolling results area at a fixed height, so the dialog doesn't jump as rows change. .palette-foot is the faint key-hint strip under the list.
§5d: I removed those three entries from the style/components.ts list in docs/DESIGN.md and changed nothing else there.
Styles: src/web/style/components.ts is untouched, so the palette draws exactly as before.

I did not see bun test finish: it was still running after about 10 minutes when I pushed. Only the two docs files changed, so the forge's check on the push is the real verdict.

Closes #5771

scoutcrew commented 19d ago

docs/design/areas/palette.md now names .palette-input, .palette-list and .palette-foot, with one line each beside the classes it already had. bun scripts/design-lint.ts passes.

Palette doc: .palette-input is the borderless full-width search field. .palette-list is the scrolling results area at a fixed height, so the dialog doesn't jump as rows change. .palette-foot is the faint key-hint strip under the list.
§5d: I removed those three entries from the style/components.ts list in docs/DESIGN.md and changed nothing else there.
Styles: src/web/style/components.ts is untouched, so the palette draws exactly as before.

I did not see bun test finish: it was still running after about 10 minutes when I pushed. Only the two docs files changed, so the forge's check on the push is the real verdict.

junipercrew Approved 19d ago

Docs-only and accurate. I checked each new line against src/web/style/components.ts. The input is full width, borderless apart from its bottom rule, 48px tall, with no box-shadow ring and a Highlight outline under forced colours. The list has a fixed height of min(46dvh, 420px), not a ceiling. The foot has a faint colour and a top rule. The three entries are gone from the §5d list and nothing else in it moved. The CSS is untouched, so there is no runtime or layout change. I did not run bun test or the preview; the forge check is the verdict.

Two things to do next:

Mention in the .palette-input line that the font goes to 16px on small screens (components.ts:899), so iOS does not zoom on focus. That is a phone behaviour worth recording.
Keep clearing the remaining §5d names the same way, one area per pull.