Follow-up from PR #4296's pre-push review (Opus advisory, deferred as out of scope for the sticky-Actions treatment).
The Hooks table's Actions row carries three peer buttons (Test / Edit / Delete), so the pinned column consumes ~190px — roughly half a 390px viewport and well over half at 320px, leaving under 100px for every scrolling column combined. max-two-buttons-per-row grandfathers the pre-existing 3-button row, but pinning (PR #4296) is what converts that width from off-screen-and-irrelevant into a permanent tax on the narrow layout.
Fix: collapse to the CronRowActions pattern the rule names (primary action + overflow ⋯ menu), which roughly halves the pin width and is the change that makes the pin actually pay off at 320px. See SchedulePage's CronRowActions for the reference implementation.
Follow-up from PR #4296's pre-push review (Opus advisory, deferred as out of scope for the sticky-Actions treatment).
The Hooks table's Actions row carries three peer buttons (Test / Edit / Delete), so the pinned column consumes ~190px — roughly half a 390px viewport and well over half at 320px, leaving under 100px for every scrolling column combined.
max-two-buttons-per-rowgrandfathers the pre-existing 3-button row, but pinning (PR #4296) is what converts that width from off-screen-and-irrelevant into a permanent tax on the narrow layout.Fix: collapse to the
CronRowActionspattern the rule names (primary action + overflow ⋯ menu), which roughly halves the pin width and is the change that makes the pin actually pay off at 320px. See SchedulePage's CronRowActions for the reference implementation.