dorfteich/apps
Claude Opus 5 70685968fc
Some checks failed
CI / Lint, typecheck, test (pull_request) Successful in 6m26s
CI / Build container images (pull_request) Successful in 1m13s
CI / Auth e2e pack (pull_request) Failing after 8m24s
CI / Import/export fidelity gate (pull_request) Has been skipped
#301: the token tables need the same scroll wrapper
The sorted report finally named it: `table.api-tokens__table` at 833px
wide, with its `.visually-hidden` heading reaching right=737 — exactly
the document's scrollWidth. Same mechanism as the sessions table, a
second table I had not wrapped.

Locally the API-tokens table was empty and therefore narrow, which is why
this only ever appeared in CI. With a token present it reproduces:
without the wrapper 345px of page overflow, with it none.

The feed-token table gets the same treatment — it is built the same way
and would fail as soon as someone holds a feed token with a long name.

The "[in fitting scroller]" marker in the report is misleading for these:
`main.main` is a scroller, but it is `position: static`, so it never
clipped the absolutely positioned heading. Only a positioned ancestor
does — which is what `.table-scroll` now is.

Verified locally against a real stack, with a wide token table present:
reflow guard green, whole a11y pack green in both colour schemes.
2026-08-01 11:34:13 +02:00
..
api #296: remove the unsubscribe-token dual-verify window early 2026-07-31 23:03:03 +02:00
backup #288: reset schema before pg_restore — partitioned tables broke --clean 2026-07-31 17:00:05 +02:00
collab #236: pin the Node version 2026-07-31 04:14:55 +02:00
web #301: the token tables need the same scroll wrapper 2026-08-01 11:34:13 +02:00