The repeat interval goes down to one second

Featurekamo-internal
Shipped
September 7, 2026 at 1:55 AM UTC
Author
Kamo
Commit
b022c21

Asked for on 2026-09-06. The floor was five; it is one everywhere now — the control, the clamp the browser applies, and the clamp the service applies. Zero is still refused, because that is not a fast repeat but a tone playing over itself with no gap at all. One second only works if the tone is allowed to sound that often, and it was not: playEventSound throttles each event to stop a burst of arrivals machine-gunning the same chime, and lead.callback.due throttles at exactly 1000ms — so a one-second repeat would have lost about half its beats, silently, depending on which kind the card happened to be. A deliberate repeat is the opposite of a burst, so it now opts out with bypassThrottle. Nothing else passes it. Also pins the half of the feature that had no test of its own: the CARD honouring holdUntilDismissed, rather than the deck deciding to pass it. Writing it caught a harness trap worth keeping — the countdown is a chain of 100ms timeouts where each one is only scheduled after React re-renders, so advancing thirty seconds inside a single act() fires exactly one tick and "it never retired" is true of every card, held or not.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing