Follow the browser's text size instead of sliding out from under it

Every length in this stylesheet that isn't a structural clearance is in
`rem`. That is the right way round — it means the page follows the
browser's font size, which is what a phone's text-size slider changes —
and it means there was a whole axis of behaviour that 320 audits had
never once touched, because every one of them ran at the default 16px.

The sweep gets a third pass: the same surfaces on the eight phone-shaped
viewports at 20px of root text, which is 125% on an Android slider.
Everything it found on its first run was caught by a check that had been
sitting there for months with nothing to say.

The page slid sideways. Three header buttons that will not break and will
not shrink — `white-space: nowrap` and a `min-width: auto` floor apiece —
were told `flex-wrap: nowrap`, so when they stopped fitting they had
nowhere to go: "Resolve Pot" ended 23px past the right edge of a 360px
window and put a horizontal scrollbar under the whole document; at 24px,
60px past the edge of a 390px one. They take a second row now on the day
they need one, and still fit on the first and still grow into it at any
ordinary size.

Figures painted over the seat next door. Which of the two type steps an
amount got was decided by counting characters — eight for one, ten for
the other — which is a guess at how wide a figure is that happens to hold
at one text size and one puck width. At 20px on a 44px puck, "$1,200" is
six characters, took no step at all, and wanted 38px of the 34 it had.
Render.fitAmounts measures now, in the batched passes fitSeatNames
already uses, and takes the separators out before it takes a step of
type: "$1200" at full size beats "$1,200" at three-quarters of it.

And the pucks grew, which the ring cannot answer. The row heights are px
tokens so an amount stepping its type down shortens its digits and not
its row — but a token is a floor, not a ceiling. At 125% the puck went
from 55px tall to 65 and twelve of them came down on each other, because
at the 44px floor a thumb needs there is nowhere narrower to search. The
two sizes a puck is written at are capped at exactly the sizes they have
always been drawn at, so nothing changes for anybody at an ordinary text
size — and the felt is a diagram, so the rule that already governed a
puck's width now governs its height. Roomy pucks are exempt; they have
the room. The same figure is in Standings in full, at whatever size its
owner asked for.

Two smaller things on the way. The landscape rail opened at its top, so
its overflow came off the bottom — where Cancel and Raise to are; it
opens at the end now, which is the same reason it is anchored low at all.
And the check that called those buttons unreachable was wrong: the rail
scrolls on purpose, and a sweep that cries wolf is a sweep nobody reads.

418 audits, clean. One shape it is not held to, with the arithmetic in
runUiAudit.js: twelve players all-in on a 360x640 phone leaves the felt
290x163 once the bar has taken 283px of the 640, and twelve 44x62 pucks
do not fit around an ellipse 163px deep. Reported as a note every run
rather than a failure every run. 1026 unit tests.

Co-Authored-By: Claude Opus 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_015bnp7xKUPFFSpwkYNFaPgb

tests/holdem/uiAudit.js

@@ -213,6 +213,26 @@ const LayoutAudit = {
     // accessibility tree, and because a fixed element does not move when the page does,
     // no amount of scrolling could bring it back. visibility:hidden puts it away; a
     // transform only moves it.
+    // A fixed panel that scrolls is a different thing from a fixed panel that doesn't,
+    // and this check could not tell them apart. The landscape rail is `overflow-y: auto`
+    // on purpose — the raise pad outgrows a 360px-tall screen the moment the text is
+    // turned up, and the stylesheet chose overflow over drawing controls on top of one
+    // another — so a button below its fold is one flick away, not lost. Reported as
+    // unreachable it is simply untrue, and a sweep that cries wolf is a sweep nobody
+    // reads.
+    //
+    // The ancestor has to be on screen itself for this to hold, which the rail is: it
+    // is `top: 0; bottom: 0`. If a scrolling panel is ever parked off the side, the
+    // thing to report is the panel, not the button inside it.
+    scrollableAncestor(el) {
+        for (let node = el.parentElement; node; node = node.parentElement) {
+            const overflow = getComputedStyle(node).overflowY;
+            if ((overflow === "auto" || overflow === "scroll") &&
+                node.scrollHeight > node.clientHeight + 1) return node;
+        }
+        return null;
+    },
+
     focusablesReachable() {
         const offenders = this.visibleControls()
             .filter(el => {
@@ -225,6 +245,7 @@ const LayoutAudit = {
                 const b = el.getBoundingClientRect();
                 return b.top >= innerHeight || b.bottom <= 0 || b.left >= innerWidth || b.right <= 0;
             })
+            .filter(el => !this.scrollableAncestor(el))
             .map(el => `${this.describe(el)} :: fixed and off-screen, so nothing can scroll to it`);
 
         return { name: "no control is parked where scrolling can't reach it", offenders };