`, so the `+` combinator fires. Sharing the `rst-menus` name group means opening it closes the account dropdown. rastrillo hides it itself above 800px, so no media query of our own is needed. ### 3. The sign-in help sentence renders inside a 28px icon badge `signin.html:31` writes `

`. In rastrillo, `rst-help` is not helper text — it is an **icon badge**: `tokens.css:1245` gives it `display:inline-flex; width:28px; height:28px; border:1px solid; border-radius:7px`. A 90-character sentence is being poured into a 28px box that centres its overflow. Hence the one-word-per-line column and the stray border stroke across the text on desktop, and text running off the left edge of the viewport on mobile. First screen, every visitor, every viewport — and it is the sentence carrying the sign-in reassurance. Reassurance delivered inside a visibly broken component reads as incompetence, not honesty. **Fix:** the attribute for field help text is `rst-field-help` (`tokens.css:1056`). Move the paragraph inside the `rst-field` so it sits under the input. --- ## P1 — the scriptless table view is a link farm `table.html:45-46` wraps every cell's content in a bare ``, and `sheets.css` styles the table but never the anchor. The result is roughly 650 default-blue underlined links per page. Empty cells render ` ` inside an anchor, producing a grid of tiny underline stubs — 650 tab stops, with no visual difference between `94200` and nothing at all. Compounding it, `--rst-border` is undefined (below), so the table has no cell borders whatsoever. Columns E–Z collapse while A–D stretch, so the grid geometry a spreadsheet depends on is gone. This is the screen the spec calls the product, and "fallback" the wrong word for. Right now it is the fallback in the apologetic sense — including in its own subtitle, which says "with no JavaScript at all": implementation vocabulary aimed at the wrong reader, describing what the view lacks rather than what it is. **Fix:** style `[data-cell-table] td > a` to inherit colour, drop the underline, and fill the cell (`display:block`, a min block size) so the target exists without being a mark; show the affordance on `:hover` and `:focus-visible` with `--rst-accent-soft`. Drop the ` `. Right-align numeric cells and set `table-layout: fixed` so sparse data keeps its geometry. --- ## P1 — five invented token names `sheets.css` uses five `--rst-*` custom properties that are defined nowhere in `tokens.css` or `theme.css`: | Token | Real name | Sites | Fallback? | |---|---|---|---| | `--rst-border` | `--rst-line` | 26, 71, 111 | **no** | | `--rst-text-mut` | `--rst-text-muted` | 49, 53, 77, 119, 135 | **no** | | `--rst-warning` | — (none ships) | 53, 93 | yes | | `--rst-font-mono` | — | 40 | yes | | `--rst-shell-bar-h` | — | 16 | yes | The three without a fallback are the ones that bite. `border: 1px solid var(--rst-border)` is invalid at computed-value time, so the whole shorthand resolves to `initial` — `border-style: none`. That is why the table view has no cell borders and the sheet bar has no divider. The five `--rst-text-mut` sites lose their colour and inherit full-strength text, so nothing muted is actually muted. `--rst-shell-bar-h` always falls back to the 3.5rem literal, so `calc(100dvh - …)` at `sheets.css:16` is wrong whenever the bar's real height differs — on mobile the sheet bar wraps to two rows and the last grid row is clipped under the fold. **Already in flight.** The session working in the primary `sheets-core` checkout has an uncommitted `internal/guardstest/csstokens_test.go` whose comment reads "the check that would have caught five invented token names shipping to a canary". It is these five. This review confirms them independently; the fix belongs to that branch, not this one. --- ## P2 — smaller, but real - **`data-contrast` is never set.** `sheets.css:88-99`'s low-contrast corner flag is well-conceived and well-commented, and it is dead code: nothing in Go, JS or any template emits the attribute. `contrast.go` computes the warned list and the notice fires, so a person is told which cells are unreadable and given no way to see which. The one Sheets-specific visual mark in the app never appears. - **"Fill down" fills one cell.** `grid.js:183-188` writes to `selection.r + 1` and stops. Every spreadsheet a collaborator has used means "fill the selected range" by that label, so they will press it repeatedly and conclude the app is broken. Either relabel to `Copy down` / `Copy right` until the range version exists, or build the range version. - **Nothing has an undo.** A cell write is a POST; browser-back does not reverse it; version history is deferred. With cell-level last-write- wins, one person can silently replace another's formula with no record either of them can see. See the open question below. - **No cell reference on screen.** To use a fill command you must remember which cell you selected. The only cue is Jspreadsheet's own header shading. - **Raw doubles as display values.** `0.10514018691588785` in the table view, clipped mid-digit in the grid. Three renderings of D2 across three surfaces, only one of them labelled. - **The grid page has no `

` — the page a working collaborator passes once and never returns to. The sheet page, where numbers are actually typed, says nothing about what is and is not protected. If the trust model is the differentiator, does it belong on the marketing surface or the working surface? 3. Is history the deferred feature, or is undo the missing primitive? In a cell-level last-write-wins grid shared by two people, undo may be what makes last-write-wins survivable at all, with history merely its readable form. The deferred table asks every deferral for a written trigger. The honest trigger here might be "the first time one of us silently overwrote the other's formula" — and that fires the day the second person joins.