Skip to content

An open source design system that's fully customizable and agent ready

TypeScript

spec(AST-094): rows of a menu that cannot scroll highlight on touch-down (FR11, DEC-14) (#8555)

Cindy Zhangbc56fd8aff7a
diff --git a/docs/specs/AST-094-touch-presentations/spec.md b/docs/specs/AST-094-touch-presentations/spec.md
index 465ea5f316..94fda268d7 100644
--- a/docs/specs/AST-094-touch-presentations/spec.md
+++ b/docs/specs/AST-094-touch-presentations/spec.md
@@ -199,7 +199,11 @@ a measured, sourced difference exists.
surface; only its press timing follows the control profile) for touch
presentations, the press treatment of `family:buttons`, and the last sentence of
`module:DropdownMenu/useMenuPress` FR6 (menu rows paint `:active` only under
- `(hover: hover)`): under a finger, menu rows take the cell profile. FR6's
+ `(hover: hover)`): under a finger, menu rows take the cell profile. A menu whose
+ rows fit (`module:DropdownMenu/useMenuPress` FR4), so it cannot scroll,
+ gives its rows no 150 ms delay: they highlight on touch-down. A list that can
+ scroll keeps the delay. A press in a list that no scroll can claim stays
+ unclaimed, which FR19 allows (DEC-14). FR6's
rule that at most one row of a menu is lit still holds, so a finger that
slides from one row to another lights only the row under it.
- **FR12 — Long press and rubber band are per use.** A long press MUST use the
@@ -533,7 +537,7 @@ FR33 apply to menus only. A mouse keeps today's behavior.
| FR6 | Unit and browser tests catching an animation mid-flight and retargeting it | catch at peak velocity; retarget with a new spring | a layout read, a jump, or a lost velocity fails |
| FR7, FR8 | Component browser tests and storyboards with and without Reduce Motion | entrance, exit, move; a drag and its lift under Reduce Motion | a missing exit, any travel, scale or spring under Reduce Motion other than a coast after a throw and its settle at an edge (`design:reduced-motion` DR2), or an opacity fade over 200 ms fails |
| FR9, FR10 | Recognizer unit tests on synthetic streams and browser tests with real touch input | drag, second finger, pinch, page zoom, main-thread block | a second finger that breaks a drag, or a page pinch blocked other than by the author's `touch-action`, fails |
-| FR11, FR12 | Press and long-press tests on synthetic streams with explicit timestamps | inside and outside a scroll view; a drag the browser takes; a lift inside; a menu row under a finger | the wrong profile's timing, a press that survives the browser taking the touch, or a control activated other than by the browser's click fails |
+| FR11, FR12 | Press and long-press tests on synthetic streams with explicit timestamps | inside and outside a scroll view; a drag the browser takes; a lift inside; a menu row under a finger; a press on a row of a menu whose rows fit and of one that scrolls | the wrong profile's timing, a press that survives the browser taking the touch, or a control activated other than by the browser's click, a row of a menu whose rows fit that waits 150 ms, or one of a scrolling menu that does not, fails |
| FR13 | Resolver unit tests and a server-render test | coarse and fine pointer; narrow, wide and short; server render; hydrating render | a component that answers the conditions differently, or a touch presentation in the server or hydrating render, fails |
| FR14 | Browser tests of a sheet over a scrolled list | scrolled and at its top | a midway handoff fails |
| FR15–FR17 | Recognizer unit tests on synthetic streams with explicit timestamps | exclusive, simultaneous, require-to-fail, nested; a watcher beside a claiming winner; a blocked main thread; a pan at 10 pt per axis | a wrong winner, a late deadline, or a translation that keeps the hysteresis, or a watcher failed or cancelled by a claiming winner fails |
@@ -685,6 +689,19 @@ UIKit's 15 px, leaving the author's scrolling untouched outside it.
Rejected: claiming `pan-x` across the whole element.
+### DEC-14 — A menu that cannot scroll highlights its rows at once
+
+**Reference:** `spec:AST-094/DEC-14`
+**Decider:** `cixzhang`, `2026-10-26`
+
+The cell delay exists so a scroll can win before a row lights. A menu whose
+rows fit cannot scroll, so it has no scroll to wait for and its rows highlight
+on touch-down; a list that can scroll keeps the delay. That a UIKit menu's
+rows likewise highlight on touch-down is a guess until a short UIMenu on the
+iOS 26.2 simulator measures it.
+
+Rejected: the 150 ms delay on every menu row.
+
## Open questions
- **OQ1 — Scroll view bounce-back curve.** What curve brings a scroll view