Say how many ways once, in the one control that owns it

"Split between" on Quick Split was two controls for one value stacked on
each other: chips 2 3 4 5, and under them a bar reading "2 ways" with a −
and a +. The count was written down three times at once — the lit chip,
the bar, and "Each of 2 players gets" in the panel above — and two of the
three were controls. 134px with its label, against 74px for "Smallest
chip in play" right below it, which offers five choices in one row.

The bar was never meant to be a bar. `.waysStepper` asked for a 150px
min-width inside a wrapping flex row, so on a phone it always wrapped to a
line of its own, and `flex: 1 1 auto` then gave it all 358px of that line:
252px of empty readout with the − and + pushed 304px apart, on a screen
390px wide. Now it is 136px with its ends 121px apart, and it only exists
once you are through the door — a fifth chip reading "6+", behind which
the stepper is where the count is written. Under six ways, which is every
chop a home game will run, the field is one row and 74px.

Two more things went with it:

Neither stepper ever disabled an end, so − at the floor and + at the
ceiling looked live and swallowed the tap. NN/G's stepper guidance asks
for the opposite. Both ends of both steppers now grey out.

The per-pot chop capped its + with `Math.max(contenderCount, MAX_WAYS)`,
which is always 12 — a side pot only P1 and P2 were eligible for would
happily chop ten ways at $12 each. It is `chopCeiling()` now, and a
two-contender pot is offered no stepper at all, that being the common
shape.

The sweep went straight to the all-in mode and audited only that, so the
mode the screen opens in had never been looked at in fourteen rounds,
which is how a 358px bar lasted this long. It audits both now — 428
audits, clean — and the first run of it found the step buttons had been
40px wide rather than 44 since they were written.

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

JoshHeaps.Net/wwwroot/css/casino/quicksplit.css

@@ -526,20 +526,30 @@ button,
     font-weight: 600;
 }
 
+/* As wide as the three things in it, and no wider.
+   This sits in the same wrapping flex row as the chips, where it has never once fitted
+   on the first line of a phone. `flex: 1 1 auto` then handed it the whole of the second
+   line: measured on an iPhone, a 358px bar with 252px of nothing in the middle and the
+   − and + pushed 304px apart — the two ends of a control a thumb is meant to work with
+   one hand. 136px now, its two ends 121px apart. */
 .waysStepper {
     display: flex;
     align-items: center;
     gap: 0.35rem;
-    flex: 1 1 auto;
-    min-width: 150px;
+    flex: 0 0 auto;
     background: #191919;
     border: 1px solid #333;
     border-radius: 11px;
     padding: 0.2rem 0.4rem;
 }
 
+/* 44 both ways, not 40x44. It had been 40px wide since the steppers were written, and
+   the sweep never said so because the only two steppers on the site are on this screen
+   and this screen was only ever audited in its all-in mode, where neither is on display
+   until a side pot has more than two contenders. The first sweep that opened the even
+   mode reported `hittable 39x43` on both ends, on every touch viewport. */
 .stepBtn {
-    width: 40px;
+    width: 44px;
     height: 44px;
     border: none;
     border-radius: 8px;
@@ -551,17 +561,26 @@ button,
     cursor: pointer;
 }
 
+/* The floor and the ceiling look like the floor and the ceiling. */
+.stepBtn:disabled {
+    opacity: 0.32;
+    cursor: default;
+}
+
 @media (hover: hover) {
-    .stepBtn:hover {
+    .stepBtn:not(:disabled):hover {
         background: #333;
     }
 }
 
+/* The count itself, now that no chip beside it is also holding one — so it is painted
+   the way a selected chip is painted, because that is what it is standing in for. */
 .waysReadout {
-    flex: 1;
+    min-width: 2.5ch;
     text-align: center;
-    color: #999;
-    font-size: 0.8rem;
+    color: #f0d9a8;
+    font-size: 1rem;
+    font-weight: 600;
     font-variant-numeric: tabular-nums;
 }