Touch presentations feel native system spec¶
{
"paths": [
"packages/core/src/Layer/holdEntranceInput.ts",
"packages/core/src/Layer/inputHold.ts",
"packages/core/src/gestures/contextRequest.ts",
"packages/core/src/gestures/tapWobble.ts",
"packages/core/src/hooks/usePager.ts",
"packages/core/src/motion/uikit/segmented.ts",
"packages/core/src/motion/uikit/slider.ts",
"packages/core/src/Swipe/useSwipeAction.ts",
"packages/core/src/dragToSnapPoints/compositorSettle.ts",
"packages/core/src/Item/Item.sharedDrag.test.tsx",
"packages/core/src/Item/Item.test.tsx",
"packages/core/src/Item/__tests__/ItemSwipeActions.interaction.browser.spec.ts"
]
}
Intent¶
A person using an Astryx product on a phone or tablet gets controls, sheets, menus, lists and navigation with native-feeling touch behavior: measured physics and gesture thresholds instead of desktop motion stretched to a finger. What a person drags follows their hand, and what they throw settles on a spring from the speed of the throw, under every pointer. In a component whose main interaction is a tap, motion that a tap, a click, a hold, a key or the program starts plays the theme's motion tokens; in a component whose main interaction is a gesture, it settles on the component's springs (FR45). This behavior is the default on every touch device, iOS and Android alike, with no opt-in, and its motion keeps running at display rate while the page's JavaScript is busy.
The behavior comes from one measured table. Its values are measured from UIKit on a named reference release, UIKit on iOS 26.2 today; each number names the release it was taken from, moving the reference to a newer release re-measures the table, and differences on older releases are noted, not targeted. Android touch devices get the same behavior. How touch behavior differs between the platforms is being explored, and the table records a separate value only where a measured, sourced difference exists.
Non-goals¶
- The timing and easing of tap-started motion in a component whose main
interaction is a tap. In such a component, motion that a tap, a click, a hold,
a key or the program starts, such as an entrance, a move or a change of value,
plays the theme's duration and easing tokens (
architecture:theme-tokens) under every pointer, a finger included (FR45). Such a component's touch exit that no gesture drives keeps its look and plays the theme's exit duration and easing, and no exit switch removes it (FR7,spec:AST-090FR14). Gestures, press tracking, a part that follows a pointer, and the spring that settles a gesture apply to every pointer (FR43, FR45). - Platform-matched look and feel: glass versus material surfaces, glyphs and chrome. This record governs behavior, and touch sizing only as FR42 states.
- WebKit embedded in a native app and the native Swift package. This record governs the web components themselves.
- Scroll physics. Scrolling stays native on every platform: on iOS an overflow area or the page is a UIKit scroll view already.
- Which components get a touch presentation, and when. Each component's own record owns its presentation.
- Equivalent internal implementations remain valid when they satisfy this contract. The modules, files and algorithms of the motion and gesture foundations belong to their architecture records.
Requirements¶
Physics¶
- FR1 — Measured values, the same everywhere. Every spring, duration and deceleration rate that a gesture's motion plays (FR45), and every rubber-band coefficient, gesture threshold, input timing and haptic moment a touch presentation uses MUST default to the measured native value for that use (FR2), and every component that plays the same motion or gesture MUST use the same value; a theme reaches the roles only through its motion knobs (FR4, DEC-15). In a component whose main interaction is a tap, motion that no gesture drives plays the theme's duration and easing tokens, not a measured value (FR45, DEC-26). No component uses a value of its own where a measured value exists. The same values apply on every touch platform; a platform gets a value of its own only where a measured, sourced difference exists (FR2).
- FR2 — Every value has a source. Each measured value MUST name its source next to it: Apple's documentation, a WWDC session, WebKit's own source where WebKit states it matches UIKit, or a measurement of UIKit on the iOS simulator naming the app, the iOS version, the method and the date. A value without one of these MUST be labelled a guess and name the measurement that will replace it. A decompilation of UIKit MAY aim a measurement and MUST NOT be a source. An owner decision MAY set a value that departs from a measurement; it names its date and the measurement it departs from.
The values this record names for menus under a finger (FR29):
| Value | Default | Source |
| ---------------- | ---------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Open delay | none in a fixed bar; 150 ms with no scroll taking the touch inside a scroll view (the content-touch delay, FR11) | owner decision, 2026-10-24, departing from UIKit on the iOS 26.2 simulator (iPhone 17 Pro), 2026-10-23, which opened a held finger's menu 150–153 ms after touch-down in a fixed position and about 303 ms inside a scroll view |
| Handoff distance | 10 pt (CSS px), straight-line, from the first position the open menu sees | measured: same setup; moves of (0, 9) and (7, 7) picked nothing, and (0, 10), (10, 0) and (9, 9) picked |
| Drift allowance | 13 pt (CSS px) of movement on the trigger before the open | unmeasured, needs a measurement or justification: a 12 pt move still opened the menu and a 14 pt move did not (OQ5) |
The scroll take distance FR20 names is 10 px (CSS px) of the finger's own
travel from where it went down: measured along one axis in Mobile Safari
26.2 on the iOS 26.2 simulator with a slow HID drag on a scrollable page,
where the last cancelable touchmove is at 10 px and pointercancel at
11 px, 2026-10-23. Measuring it straight-line for a diagonal drag is a guess
until a diagonal drag on the same setup measures it.
- FR3 — Native physics. Springs MUST follow UIKit's spring model
(response and damping ratio, mass, stiffness and damping, and the release
velocity), with overdamping clamped to critical damping wherever UIKit
clamps it. A momentum coast MUST decay like a UIKit scroll view (0.998 per
millisecond, 0.99 for the fast rate), a drag past an edge MUST resist with
UIKit's rubber band
(1 − 1 ÷ (x·c ÷ d + 1))·dwith the coefficient its use measures (0.55 for a scroll view and a sheet), and a release MUST pick its rest point by projecting its velocity the way its UIKit counterpart does: with a deceleration rate, or with a measured projection time. A paging scroll view (the pager, and a Carousel givenhasSnap={useSnapPaging()}where the pager runs, an opt-in undercomponent:CarouselFR7) picks its rest page as its UIKit counterpart measures it, with no projection: the nearest page, or the next page in the release's direction when the release is at leastpaging.release.advanceSpeed(300 pt/s) fast, at any position on the page. It moves at mostpaging.release.maxPagesFromStart(one page) from the page the drag started on, and a release moving back toward that page stays on it (FR37). Both values are measured on the iOS 26.2 simulator, 2026-10-23: steady releases at 10, 25 and 40 % of a 402 pt page stay at 292.7–298.6 pt/s and advance at 310.7–329.9 pt/s; releases at rest stay at 45–48.5 % and advance at 55–57.5 % (DEC-25). -
FR4 — Touch motion uses named roles. Every spring, duration and curve a touch presentation plays for a gesture (FR45) MUST be a motion role named for its use (
architecture:theme-tokensINV3), with one exception. A gesture-driven exit (a release that closes or dismisses) may play a spring measured from the platform reference without a named motion role (FR45); its component's motion table lists that spring with its platform source. Every other gesture-driven motion plays a motion role. The roles this record names are listed below with their defaults and sources; further roles a component's own record measures join through the generated motion role table (DEC-5). With tempo 1 and character standard, every role plays its measured value exactly (FR1, FR2); a theme's tempo scales durations and its character offsets bounce through fixed per-role weights (spec:AST-108FR3), and roles on the fixed list ignore both: the on-screen keyboard (spec:AST-099FR8); gesture thresholds, the content-touch delay, and momentum (spec:AST-002FR3); finger tracking, the rubber band, the press model's onset delay, cancel distance, and tap flash (spec:AST-108FR4), and busy loops; and the 200 ms Reduce Motion cap. The per-role tables stay internal (DEC-15). A component MUST read touch motion through these roles and MUST NOT play a literal, apart from that measured gesture-driven exit spring. A theme's knob values MUST reach the motion at its start, without changing how the motion runs (FR5, FR6). Motion that must stay in step with the on-screen keyboard is not a theme role: it rides the keyboard's own motion (spec:AST-099FR8,architecture:react-component-runtimeINV11). Gesture thresholds, the timings that decide who gets a touch (the content-touch delay, the scroll brake, momentum memory), hold durations, flick speeds and haptics are measured input values, not motion: they are not motion roles, they stay internal and are not public concepts (spec:AST-002FR3), except theflickThresholda product passes tospec:AST-107's snap-point drag. The three knobs join the motion configuration ofarchitecture:theme-authoring-contractandarchitecture:theme-tokens(spec:AST-108). It departs from the draftdesign:motionDR3 wherever the native motion settles with an overshoot or stretches with a rubber band.Role Default Source springs.fingerTrackingresponse 0.15 s, damping ratio 0.86 Apple: SwiftUI interactiveSpring()springs.emphasisduration 0.5 s, bounce 0.3 Apple: SwiftUI .bouncysprings.settleduration 0.5 s, bounce 0 Apple: SwiftUI .smoothsprings.quickChangeduration 0.5 s, bounce 0.15 Apple: SwiftUI .snappysprings.viewChangemass 3, stiffness 1000, damping 500 measured: UIKit UISpringTimingParameters(), iOS 26.2 simulator, 2026-10-23springs.timedChangeduration 0.5 s, bounce 0 Apple: UIKit UIView.animate(springDuration:bounce:)springs.stateChangeresponse 0.55 s, damping ratio 1 Apple: SwiftUI Animation.defaultsprings.directChangeresponse 0.5 s, damping ratio 0.825 Apple: SwiftUI .spring(response:dampingFraction:)springs.menuOpendamping ratio 0.8, response 0.32 s measured: UIMenu opening, iOS 26.2 simulator, 2026-10-23 springs.menuClosedamping ratio 0.85, response 0.35 s measured: UIMenu closing, iOS 26.2 simulator, 2026-10-23 springs.subMenuOpendamping ratio 0.85, response 0.4 s measured: UIKit's own spring for UIMenu's sub-menu opening, iOS 26.2 simulator, 2026-10-24 springs.subMenuBackdamping ratio 1, response 0.4 s measured: UIKit's own spring for UIMenu's sub-menu header back, iOS 26.2 simulator, 2026-10-24 springs.contextMenuLiftdamping ratio 0.8, response 0.32 s measured: UIContextMenuInteraction's preview lift, iOS 26.2 simulator, 2026-10-23 springs.contextMenuDismissdamping ratio 0.85, response 0.35 s measured: UIContextMenuInteraction's dismissal, iOS 26.2 simulator, 2026-10-23 springs.contextMenuMorphdamping ratio 0.8, response 0.3 s measured: UIContextMenuInteraction's menu entrance and preview shadow, iOS 26.2 simulator, 2026-10-23 segmented.selectionSpringresponse 0.4 s, damping ratio 0.85 measured: UISegmentedControl's selection slide, iOS 26.2 simulator, 2026-10-23 segmented.liftresponse 0.25 s, damping ratio 1 measured: UISegmentedControl's lens lift and settle under a finger, iOS 26.2 simulator, 2026-10-23 timing.stateChangeMs250 ms measured: Core Animation's implicit transaction, iOS 26.2 simulator, 2026-10-23 timing.curves.viewChangecubic-bezier(0.25, 0.1, 0.25, 1) Apple: CAMediaTimingFunctionName.defaulttiming.curves.exitcubic-bezier(0.42, 0, 1, 1) measured: UIKit's ease-in, iOS 26.2 simulator, 2026-10-23 timing.curves.entrancecubic-bezier(0, 0, 0.58, 1) measured: UIKit's ease-out, iOS 26.2 simulator, 2026-10-23 timing.curves.movecubic-bezier(0.42, 0, 0.58, 1) measured: UIKit's ease-in-out, iOS 26.2 simulator, 2026-10-23
The three springs.contextMenu* rows are measured for ContextMenu's lift,
and component:ContextMenu owns them (DEC-5).
In a component whose main interaction is a tap, a role plays only for motion a
gesture drives: a release's settle, a flick, a pan's or a pinch's settle, a
rubber band's return, and a follow. In a component whose main interaction is a
gesture, its roles also settle the moves a tap, a key or the program starts
(FR45). The theme's tempo scales a gesture's spring's duration and its
character offsets the role's measured bounce by the role's fixed weight
(spec:AST-108 FR3); the follow itself and the rubber band stay fixed
(spec:AST-108 FR4). The rows measured for motion that a tap, a hold, a key
or the program starts, an exit included (springs.menuOpen,
springs.menuClose, springs.subMenuOpen, springs.subMenuBack, the three
springs.contextMenu* rows, timing.stateChangeMs, timing.curves.entrance
and timing.curves.move) stay as the measured native reference. No motion
that a tap, a hold, a key or the program starts in a component whose main
interaction is a tap plays them: that motion plays the theme's duration and
easing tokens (FR45), and an exit plays the theme's exit duration and easing
(FR7). Two approved motions keep their springs until their own records change:
the animator's animate (spec:AST-107 FR3) and useDragToSnapPoints's
settleTo (spec:AST-107). AST-105's glide, swap and edge reveal are
tap-started layout motion and play the theme's curve tokens, except a
gesture's release, which settles on its spring (spec:AST-105 FR4). Reduce
Motion substitutions and continuous busy loops (such as
ProgressBar's indeterminate pulse, component:ProgressBar FR6) keep their
named roles; they are neither gesture- nor interaction-started motion. A
component's own record states which of its roles a gesture drives.
The pager's measured settle after a release (DEC-25) is not an exit, so FR4's
exception does not cover it. It follows the theme's tempo: a settle from
rest keeps its shape and takes tempo times as long, and a release still
starts at 96 % of the finger's speed, as at tempo 1. Implementation gap: it
plays UIKit's measured settle without a named role, and it doesn't yet
follow character.
Implementation gap: the pager is a gesture component, so its animated scroll
to a page that the program asks for settles on the pager's spring from rest
(FR45); today it plays a 300 ms scroll on a sinusoidal curve.
Implementation gap: the sheet picker wheel's snap rate (UIKit's measured picker deceleration) plays from an internal constant and is not yet a named role; a role kind for rates comes with a later change.
Motion¶
- FR5 — Motion runs on the compositor. Every release and every
programmatic animation of a touch presentation MUST animate
transform, the individualtranslate,scaleandrotateproperties, oropacity(a dialog's::backdropincluded) through Web Animations that the browser runs off the main thread, and MUST keep advancing at display rate through a main-thread block. It MUST NOT animate layout properties, and MUST NOT step a frame from script when the compositor can run the curve. A snap-point drag whose parts read one custom property settles throughdragToSnapPoints/compositorSettle.ts: onetranslateanimation per part, from one spring on one clock. The animator cannot do this: its custom property animates on the main thread, and itstranslatemoves one element. A press shows at once. Every press release that fades does so on the theme's exit motion tokens (--duration-exit,--ease-exit), on every device and pointer, by the owner's decision (2026-11-03); under Reduce Motion,design:reduced-motionDR2 applies. - FR6 — Motion is interruptible. A finger MUST be able to catch any
animation mid-flight at the value on screen. That value and its velocity
MUST come from the curve, not from a layout read. A new target MUST keep the
current velocity, and a release MUST hand its velocity to the spring that
follows.
A pager's release slower than
paging.release.velocityFloor(225 pt/s) starts its settle from rest, as UIKit's does; a faster release hands its velocity to the settle. The floor is a guess inside the measured bracket (UIKit zeroes steady releases at 175 and 200 pt/s and keeps 249 pt/s, iOS 26.2 simulator, 2026-10-23) until a measurement replaces it (FR2). A page change during a drag starts from rest (DEC-25). A resize during a settle retargets it. When the spacings between pages all scale by one ratio, the settle keeps its page and its fraction of a page. Otherwise a settle toward the last page ends on the last page. Any other ends on the page nearest its target's offset, a tie going the way it moves. A settle that began before the viewport had a width lands on its target at once when the viewport gets one. A finger or a pen that lands on a pager's settle after a release never reaches the pager's content: no press feedback and no click. UIKit's content took none of 30 such touches (iOS 26.2 simulator, 2026-11-06). A finger or a pen that lands on a pager'sgoTomove stops it at the touch, and the lift settles on the nearest page; the content still takes the tap. UIKit's animatedsetContentOffsetstopped 2 to 23 ms after the touch, and its content took 24 of 30 taps (iOS 26.2 simulator, 2026-11-06). A rebase toward the new rest shifts a spring heading there whole: its curve and target move by the rest's change, and it keeps its start time and velocity. On a starved page, the Switch's value change then shows no step in its frame proofs. A retarget's spring that the browser commits late starts at that frame, from the value on screen there, as UIKit's added spring begins at its commit (iOS 26.2 simulator, 2026-11-07). Late means more than 34 ms after the first call that frame commits; a sooner commit keeps the call's clock. It keeps the velocity on screen, or one its call hands it, such as a release's. A played curve or a coast that retargets keeps the call's clock. Calls made in one callback, such as one event listener or one observer callback, share the clock of its first call, so several elements line up; a call more than 34 ms after that first call starts a new clock. A swipe row's close that a touch tap on its content, Escape or a press outside it starts is made in that input event's own task. It uses the animator's internalstart: 'next-frame'(architecture:react-component-runtimeINV13). The first frame after the task commits it, however long a later listener holds the page, so the close never skips ahead into its curve. - FR7 — Exits keep the native counterpart's look. A touch presentation MUST
play an exit with the look of its UIKit counterpart's exit, on every touch
platform: a menu shrinks into its trigger, and an alert fades. In a component
whose main interaction is a tap, an exit that a tap, a key, an outside press
or the program starts plays the theme's exit duration and easing,
--duration-exitand--ease-exit(spec:AST-090FR14, FR45). A component whose main interaction is a gesture, such as a sheet or the Lightbox, plays every exit on its spring: a close that a tap, a key, an outside press or the program starts plays the same settle as a swipe close, from rest, and an exit that a gesture drives starts from the release velocity (FR38, FR45). The theme's exit switches never remove a touch exit (spec:AST-090FR14). FR8 governs their reduced-motion form. Each overlay's own record states its exit, since members own their animation (family:overlay-dismissalAV6). -
FR45 — A component's main interaction picks springs or the theme's motion tokens. A component whose main interaction is a gesture plays springs for its motion, including moves a tap starts inside it (a tap on a sheet detent or a close button settles on the same spring), so its pieces stay coordinated. A component whose main interaction is a tap plays the theme's curve tokens (duration and easing, scaled by
tempo), never a spring, since a tap carries no velocity; no character or option plays a platform-measured curve for it (owner decision, 2026-11-04). Gesture-driven motion where the release velocity matters plays a spring that starts at the gesture's velocity (the settle, a fling, the rubber-band return), or for a coast its measured deceleration rate from that velocity, under every pointer (FR43). In a component whose main interaction is a tap, a motion a tap, key or the program starts whose record names no duration step, and for which the platform has a measured duration, plays the theme duration token whose value in the Storybook theme (neutral) is nearest that measurement, with the easing for its kind (entrance, exit or move); the measured value stays a reference in the component's motion table. A motion whose record names its step keeps it: a tap-started overlay exit plays--duration-exitand--ease-exit(FR7); an in-place toggle cross-fade is not an exit, andcomponent:ProgressBarFR4's fill keeps--duration-medium. In a tap component, small anchored surfaces (a popover, a menu, a toggle, a row) and full-screen surfaces (a Dialog, an AlertDialog) each take their own platform measurement; no kind of motion without a named step defaults to one duration step. Springs follow the theme'stempo: tempo scales a spring's speed and leaves its bounce unchanged. Each spring pairs with a timing tier, so its settle and its companion curves finish together: menu springs with--duration-medium-min, sheet and sub-menu springs with--duration-medium, settle and emphasis springs with--duration-medium-max. In a tap component, quick taps and presses keep timing tokens and no spring. At tempo 1, every measured spring keeps its platform feel (owner decision, 2026-11-04). A gesture is a continuous pointer movement whose velocity carries into the motion: a drag, a flick, a swipe, a pan, a pinch, and the settle and rubber-band return after any of them. The theme'stemposcales the spring's duration and itscharacteroffsets the role's measured bounce by the role's fixed weight (spec:AST-108FR3); the follow and the rubber band themselves stay fixed (spec:AST-108FR4). A part that follows a pointer follows it under every pointer (FR43). A swipe row that a finger holds plays no follow spring: from its claim on the touch its offset is the finger's travel since touch-down at every frame until the release, plus the lead it gains past the confirm point (DEC-32). In a component whose main interaction is a tap, every other motion, which a tap, a click, a hold, a key or the program starts, MUST play the theme's motion tokens, its duration and easing tokens scaled bytempo(architecture:theme-tokens,spec:AST-108FR2), under every pointer, a finger included. Two approved motions keep their springs until their own records change: the animator'sanimate(spec:AST-107FR3) anduseDragToSnapPoints'ssettleTo(spec:AST-107). AST-105's glide, swap and edge reveal are tap-started layout motion and play the theme's curve tokens, except a gesture's release, which settles on its spring (spec:AST-105FR4). Reduce Motion substitutions and continuous busy loops (such as ProgressBar's indeterminate pulse,component:ProgressBarFR6) keep their named roles; they are neither gesture- nor interaction-started motion. A tap has no velocity, so it is not a gesture. Springs drive the motion of a component whose main interaction is a gesture; curve tokens (a duration plus an easing) drive the motion of a component whose main interaction is a tap. Spring and curve timing share that one coordinated scale, so the theme's tempo scales both; the spring tiers are listed below (implementation gap: springs are tuned independently today). A touch presentation keeps its own look for that motion (FR13), such as a menu that grows from its trigger, and plays it on those tokens. A press that starts as a tap or a hold and continues as a drag springs from the drag's release. In a component whose main interaction is a tap, a touch presentation's exit that no gesture drives plays the theme's exit duration and easing, and no exit switch removes it (FR7,spec:AST-090FR14). Gesture thresholds, the timings that decide who gets a touch, hold durations, flick speeds, the press model's clocks and haptics are measured input values, not motion roles, and stay internal as FR4 states. Under reduced motion,design:reduced-motiongoverns both kinds (FR8, FR38, FR43). Companion motion inside a component (a sheet's scrim fade, handle and content fade or scale, a Lightbox's chrome fade, a menu's backdrop) runs on the pace of the component's main motion: it derives from the main spring's progress and settle time in a gesture component, or from the main curve's duration and easing in a tap component, and never runs on independent timing.Main interaction Motion Components Gesture Springs BottomSheet, Drawer, swipeable List rows, Lightbox, the pager and Carousel, ContextMenu's long-press presentation, Slider, pull-to-refresh Gesture Springs: a tap, key or program turn plays springs.settlefrom rest; the flick coast keeps UIKit's measured deceleration; the slow-release snap stays as recordedthe DateInput and TimeInput wheels Tap Curve tokens Accordion, Disclosure, Collapsible, DropdownMenu, Popover, Tooltip, HoverCard, Dialog, AlertDialog, Tabs, Checkbox, press feedback Gesture-capable Springs under a touch presentation: the thumb drags, so every tap, click, key or value change settles on the same spring; without a touch presentation they keep the theme's curve (owner decision, 2026-11-04) Switch, SegmentedControl Open (as its record states today) Theme timing for a tap dismiss; a spring from the release for a swipe Toast
Toast keeps the motion its record states today: theme timing for a tap
dismiss, and a spring from the release for a swipe (component:Toast FR5).
Which main interaction classifies it is open.
| Spring roles | Timing tier |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
| `springs.menuOpen`, `springs.menuClose`, `springs.contextMenuLift`, `springs.contextMenuDismiss`, `springs.contextMenuMorph` | `--duration-medium-min` |
| `springs.subMenuOpen`, `springs.subMenuBack`, and a sheet's springs | `--duration-medium` |
| `springs.settle`, `springs.emphasis` | `--duration-medium-max` |
| `segmented.selectionSpring`, `springs.directChange`, `springs.quickChange`, `springs.stateChange`, `springs.timedChange`, `springs.viewChange`, `springs.sliderLift`, `springs.sliderDrop`, `springs.sliderRelease` | no tier named yet |
| `springs.fingerTracking` | none; a follow stays fixed (`spec:AST-108` FR4) |
- FR8 — Reduce Motion. Under reduced motion, touch presentations follow
design:reduced-motionDR2 and DR4.
Gestures¶
- FR9 — A finger is tracked off the render path. A drag MUST follow the finger with one visual update per move, with no component render per move and no layout read after the gesture begins. Native scrolling MUST be used only where the component is a scroll view (lists, scroll areas, the page). A component MAY track a finger with native scroll snapping only with simulator evidence that it tracks through a main-thread block, ends on the native release curve, ends correctly when the finger lifts during a block, and lets a finger catch the content mid-flight.
- FR10 — A second finger never breaks the first. A second finger MUST NOT
cancel or redirect a drag a recognizer has claimed. Page pinch-zoom MUST stay
the browser's whenever no pinch recognizer claims the fingers, no drag is
claimed, and the element's author
touch-actionkeepspinch-zoom(FR18; WCAG 1.4.4). A menu's press-tracking slide keepsmodule:DropdownMenu/useMenuPressFR4: a second pointer orpointercancelends its gesture with nothing acting, which keeps the page zoomable over an open menu. - FR11 — Three press profiles. Press feedback MUST follow one of three
profiles. A control (UIControl) highlights on touch-down outside scroll
views and activates by the browser's click on a lift inside. On the web a
control's press ends when the browser takes the touch (FR20), and its
activation stays the browser's click, except that an action a
family:action-groupsmember tracks activates at the lift (FR26), and a toggle underspec:AST-020FR9's slide-off exception (Switch, Checkbox, CheckboxListItem) may also complete on a lift after the finger slid off; and a Switch completes its own toggle at the lift of a finger hold or a flipping drag, rather than through the browser's click (component:SwitchFR15); and a SegmentedControl drag commits at the lift on the segment nearest the pointer, wherever it began (component:SegmentedControlFR13). Where the engine hit-tests an element a compositor animation moves at the motion's start (iOS WebKit), a touch on moving content goes to what was drawn under the finger at touch-down, and a tap there (no recognizer claimed it, the browser did not take it, and it stayed within 45 pt) MUST activate it: the browser's own click for that touch is cancelled or swallowed, and that element receives one click, an editable focused first. A pager's settle after a release is the exception: a finger or a pen that lands on it never reaches the content (FR6). Under a fine pointer a control uses a third profile with no delay: its press paint starts at once onpointerdown, through the same press controller and release fade as a finger's, in place of CSS:active; the scroll brake stays touch-only (DEC-21). A cell (a table or collection cell) highlights 150 ms after touch-down inside a scroll view, drops the highlight when the scroll wins (FR20), and activates on a lift inside it with no scroll taking the touch (FR20). A control is inside a scroll view when it sits in a scrollable container, or in scrolling page content with no fixed ancestor; a control in a fixed bar (a top bar, a tab bar, a toolbar) is not. A control inside a scroll view takes the same 150 ms delay before its highlight and then follows its control profile; the 150 ms delay applies only inside scroll views. A control whose own record keeps its press through a drag keeps it: Slider's overlay stays on the dragged thumb (design:user-statesDR4). On every touch platform this amendsdesign:user-statesDR1 (the pressed overlay during a hold) and DR3 (a held, selected SegmentedControl item keeps its raised selected surface; only its press timing follows the control profile) for touch presentations, the press treatment offamily:buttons, andmodule:DropdownMenu/useMenuPressFR6: under a finger, menu rows take the cell profile. A menu whose rows fit (module:DropdownMenu/useMenuPressFR4), 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. A theme's:activeoverride paints with the component's own press paint: under a coarse pointer only while Core believes the press (data-astryx-press="on"on the pressed element or around it), so a scroll that starts on a control never shows it; under a fine pointer from the press's start. - FR12 — Long press and rubber band are per use. A long press MUST use the thresholds its UIKit counterpart uses: 0.5 s and 10 pt for a plain long press, the measured values for context menus and menus. A rubber band MUST use the coefficient its use measures.
- FR13 — One rule for the touch presentation. A touch presentation applies
under a coarse primary pointer, and only after hydration: a server render and
the hydrating render produce the pointer presentation (
spec:AST-013FR9). Where a presentation also depends on size, compact is governed byspec:AST-012FR9 andarchitecture:public-component-apiINV17. A presentation asks for exactly the conditions its own record names (the date and time sheet asks for the pointer only,spec:AST-043FR1). A style keyed on the literal touch media query conforms, since the server and hydrating markup are identical (DEC-6). A touch presentation is the look and press timing a component adds under this condition: a lift, a sheet in place of a popover, a grow from the trigger, hit-area growth (FR42), touch press timing (FR11) and haptics (FR23). It never decides whether a part follows a pointer or whether a gesture's settle springs (FR43, FR45). In a tap component its other motion plays the theme's duration and easing tokens, and in a gesture component its springs (FR45); its exit plays as FR7 states. - FR14 — Nested scrolling follows the native rule. Who gets a drag that
starts inside a scroll area MUST be decided once, when the drag begins. If
the area sits at its edge and the drag moves toward that edge, the
surrounding surface (a sheet) takes the drag; otherwise the area keeps it for
the whole gesture and rubber-bands at its edge. The drag MUST NOT change
hands midway, in either direction, with one exception (DEC-28). At a
sheet's tallest detent, a pull that carries its content past its end
continues as the sheet's stretch, and a reversal hands it back to the
content (
component:BottomSheetFR18). This amendsspec:AST-025FR14 (scroll chaining by default) for touch presentations on every touch platform. - FR15 — Recognizers arbitrate like UIKit's. Recognizers that see the same touch sequence MUST be exclusive by default: the first to recognize wins and the others fail, unless both allow simultaneous recognition. A recognizer that requires another to fail MUST hold its recognition until that one fails, and MUST fail if that one recognizes. When several recognize on the same event, the innermost element's recognizer MUST win. Watchers are exempt from this exclusivity: they recognize alongside a claiming winner, which never fails or cancels them (DEC-7).
- FR16 — Gestures keep the event clock. Recognizers MUST read time from the input events' timestamps. Durations (a long press, the interval between taps) MUST be deadlines on that clock, so a blocked main thread delays the report and never the moment reported.
- FR17 — Native readings. A recognizer's thresholds MUST follow UIKit's
measured values (FR1, FR2). A pan begins at 10 pt of travel on either axis (a
screen-edge pan attached to an element within the band at 15 px, FR18),
and its translation excludes that travel. Release velocity is governed by
spec:AST-100. - FR18 —
touch-actionleaves the browser the rest. An element with touch recognizers MUST get atouch-actionthat leaves the browser exactly what its recognizers do not use: the other axis for an axis-limited pan or swipe,manipulationfor taps and long presses, everything for a one-way pan or a pan that shares its axis with native scrolling.pinch-zoomMUST stay unless a pinch or rotation recognizer is attached. The derived value is intersected with the element's own authortouch-actionand is never wider than it (DEC-8); when the author's value leaves outpinch-zoom, the author's value wins. A screen-edge pan claimspan-xonly for a touch that lands in the edge band, 40.2 px wide at that edge (UIKit's measured edge region on a 402 px wide screen; that it scales with the screen's width is a guess until a second screen width measures it), and inside the band it decides at 15 px of travel (UIKit's screen-edge hysteresis); outside the band the author's scrolling is untouched, and FR19's 10 px governs every other claim (DEC-13). The band'span-xclaim and 15 px start apply where the screen-edge pan is attached to an element that lies within the band; on an element that reaches beyond it, whosetouch-actioncannot claim per touch, a touch in the band decides at FR19's 10 px like every other claim. - FR19 — Claims are made in time and only by an owner. Recognizers attach for every pointer, with FR43's
exceptions. This rule governs
this record's behaviors only;
spec:AST-057keeps its per-event pointer read for the row swipe, as its record states. Afamily:action-groupsmember that tracks its group (family:action-groupsFR1) keeps, as FR24 allows, onepointerdownlistener on the group element, cancelable where the member needs it, adds document listeners only during a press, removed at the release, and may arm one per-document click swallower from the release until that gesture's click (DEC-17). A recognizer that begins MUST claim its touches by cancellingtouchmovethrough a non-passive listener on its element; a watcher, which never claims, is exempt (DEC-7). Atouchmoveof a touch no recognizer owns MUST NOT be cancelled, with five exceptions. While a scroll lock under a modal presentation holds the page, it MAY cancel the moves of a one-finger touch that no recognizer owns when that pan would scroll the page; a second finger is never cancelled (FR10), and the page keeps pinch-zoom. A modal overlay that takes the page scroll lock also stops the page's pull-to-refresh and overscroll bounce while it holds the lock, and releases them with it. Once its press is delivered, a control that keeps its press through a drag (FR11) owns its touch and MAY cancel that finger's moves. A scroll-edge pan, such as a sheet's pull from a scroll area at its edge (FR14), MAY cancel its touch's moves from the first move, only while every scroller under the finger sits at its edge and the drag moves toward that edge (FR14), and only the moves the browser would rubber-band, never a real scroll; the pan itself still begins at FR17's 10 pt, as UIKit's sheet pull does (DEC-18). A scroll-edge pan that waits out a tap's wobble before cancelling MUST still cancel before a kept move could commit the native pan (DEC-29). A toast's swipe MAY cancel its touch's moves from a first move toward its dismiss edge (component:ToastFR4). A recognizer that is cancelled while its touch is moving, other than by the browser taking that touch (FR20), such as a long press dragged past its tolerance after it began, keeps owning that touch until it lifts and MAY cancel its moves, so the drag never becomes a page scroll midway (FR14); a touch that is resting when its recognizer is cancelled, and every touch of a recognizer that requires another to fail when that one recognizes, is given back (FR10). A recognizer that competes with native scrolling MUST decide within 10 px of travel, before the browser commits to the scroll; a screen-edge pan on an element within its band, which leaves the browser no horizontal scroll, decides within 15 px, and one on a wider element within 10 px (FR18). Only an element with a recognizer that must claim mid-gesture registers that blocking listener; an element whose recognizers decide only at the lift keeps itstouchmovelistener passive, and itstouchendlistener stays cancelable so the gesture can cancel the click (FR21). While an element that holds, or sits inside, an element with a recognizer that claims moving touches moves on the compositor (iOS WebKit), the document MAY carry a non-passivetouchmovelistener; it cancels only the moves of a touch a recognizer owns under this rule and comes off when the motion ends. While it is on, a native scroll that starts anywhere on the page waits for a free main thread. Known limit: a native scroll that starts on an element with a blocking listener waits for a free main thread in iOS Safari and Chromium. That is never worse than UIKit, whose scrolling stops on a busy main thread, and a passive listener, or one added attouchstart, would hand diagonal drags to the scroll. - FR20 — The browser can take a touch.
pointercancel, a finger's first uncancelabletouchmove, or a native scroll under the touch MUST count as the browser taking the touch, thetouchmoveonly when the browser could scroll along the finger's main axis, and a native scroll only once that finger has moved the scroll take distance (FR2), so sub-pixel movement under a still finger does not cancel a tap (DEC-8): possible recognizers that share it fail, active ones are cancelled, and the view's press is cancelled without a release. The main axis is the one the finger has moved farther along since touch-down, horizontal on a tie; the browser could scroll along it when a scroller under the touch has room that way and everytouch-actionbetween them allows that pan (FR18). Later uncancelable moves of that finger never count. A recognizer that never claims (a watcher) registers only passive listeners (architecture:react-component-runtimeINV3, INV5), and a watcher is not cancelled when the browser takes the touch: it follows the scroll to the lift (DEC-7). - FR21 — Clicks follow the gesture. When a gesture takes a touch, its
touchendMUST be cancelled, and no click or compatibility mouse event reaches the page. The click guard that the gesture host arms at that lift takes them: the click, and the latemousedownandmouseupthat WebKit sends after a held tap's cancelledtouchend. A click held for a recognizer that may still recognize (a tap that a double tap may claim) MUST be replayed on its target if that recognizer fails. Activation withdetail === 0(keyboard, assistive technology) MUST always pass. A tap MUST NOT wait for the browser's double-tap delay. - FR22 — The platform keeps its edge gestures. iOS Safari's back swipe from the screen edge and Android's system back gesture MUST stay the browser's and the system's; a touch presentation never overrides them.
Menus and popovers under a finger¶
FR26–FR28 and FR30 apply to every surface that carries the press model of
module:DropdownMenu/useMenuPress (DropdownMenu, ContextMenu, their sub-menus,
and Selector's listbox, whose options count as rows) under every pointer
(FR43); FR29 applies to DropdownMenu's trigger under the same
condition; FR34 applies to menus;
FR31 applies to anchored menus and to Popover under a finger, and FR35 to
the entrances it lists; FR32 and FR33 apply to menus only. A mouse keeps
module:DropdownMenu/useMenuPress FR1–FR3 and DEC-3, so a mouse released
outside a menu closes it.
FR26–FR28 are the shared rule of family:action-groups: every member, not
only menus, follows them under the family's scope (DEC-17). Whether a menu
stays open after a release outside it stays with the menu: FR28 keeps it open
under a finger, and a mouse follows module:DropdownMenu/useMenuPress FR3 and
component:Selector FR7.
- FR26 — The lift decides. A menu row MUST act when the finger lifts over it, never because the press began on it; a press that never left its row is a tap and acts on that row. One gesture acts at most once: the browser's click for that gesture acts on nothing.
- FR27 — The highlight follows the finger. While a finger is held in an open menu, the lit row MUST be the enabled row under it, and nothing is lit over a divider, a heading, a disabled row or outside the menu. At most one row is lit; the row the press began on keeps no pressed look once the finger leaves it (FR11).
- FR28 — A lift outside keeps the menu open. A finger that began inside a menu and lifts outside it MUST act on nothing and leave the menu open. A second finger ends the gesture, as a lost focus or a cancelled touch does (FR44): nothing acts and the lit row clears.
- FR44 — A lost focus or a cancel ends every press. A window blur, or the browser cancelling the pointer, ends any press the gesture host tracks, on every surface and for every touch and pen, and nothing acts at the later lift; a mouse button held through the blur keeps its click.
- FR29 — DropdownMenu opens on press, with the opening finger's
handoff. This rule covers DropdownMenu's trigger only; ContextMenu,
sub-menu rows and Selector keep their own opening. Under a finger, a
DropdownMenu trigger in a fixed bar MUST open its menu as the finger
presses. A trigger inside a scroll view (FR11) MUST open it once the 150 ms
content-touch delay has passed with no scroll taking the touch (FR20), or at the lift of a tap that
ends sooner; a scroll that takes the touch first (FR20) takes it and nothing opens. Before the open, the finger may move no
more than the drift allowance (FR2). After an open under a held finger,
nothing is lit and a lift acts on nothing until the finger has travelled
the handoff distance from the first position the open menu sees; from then
on FR26–FR28 apply.
presentation="popover"keeps today's open on a tap; the default is unset (architecture:public-component-apiINV16). The delay and distances are internal values and gain no new props (spec:AST-002FR3); Amodule:DropdownMenu/useMenuPresscaller that sets the releasedlongPressDelayMsgets that wait in a fixed bar and in a scroll view alike, which keeps the released behavior (spec:AST-017FR3). - FR30 — Edge autoscroll under a finger. While a finger is held in a menu that scrolls, resting near its top or bottom edge MUST scroll the menu toward that edge, and the lit row MUST follow the row now under the finger. The scrolling stops when the finger leaves the edge, the menu reaches its end, or the gesture ends.
- FR31 — Menus and popovers grow from their trigger and shrink back.
Under a finger, on every touch device, an anchored menu or a Popover MUST
open by growing out of its trigger and close by shrinking back into it. The
grow plays on the theme's entrance duration and easing tokens (FR45); the
shrink plays on the theme's exit duration and easing (FR7). The shrink plays in full after the surface has
closed. This is its exit under FR7 (
family:overlay-dismissalAV6); under reduced motion FR8 applies. A menu or popover presented as a bottom sheet follows the sheet instead. - FR32 — A pan outside dismisses. Under a finger, an open anchored menu MUST close as a touch outside it
begins to pan, and at the lift of a tap or hold outside it. A Popover's
dismissal is unchanged. A pinch stays available over it: its surface
never takes
touch-action: none, so the page keeps zooming unless the author's owntouch-actionleaves outpinch-zoom(FR10, FR18; WCAG 2.2 SC 1.4.4). Listening for that outside touch costs nothing once it ends (FR24). A menu whose caller passespresentation="popover"keeps its released outside dismissal (FR25). - FR33 — A ContextMenu under a finger. With a finger or pen, the long press
that opens a ContextMenu MUST NOT close it at the lift, and a press outside it
follows FR32. After a held finger opens it, nothing is lit and a lift acts on
nothing until that finger has travelled the handoff distance (FR2) from the
first position the open menu sees; from then on FR26–FR28 apply. On every
touch device, a ContextMenu that a held finger opens on a block trigger MUST
lift the trigger above the page and show the menu beside it, with no row lit.
A tap outside closes the menu and reaches nothing beneath it, and closing
returns the trigger to its place. ContextMenu's long-press presentation is a
gesture component, so the lift plays
springs.contextMenuLift, the menu's growsprings.contextMenuMorph, and the return, part of the menu's exit,springs.contextMenuDismiss(FR7, FR45). Under reduced motion FR8 applies. An inline trigger keeps today's menu, a menu presented as a bottom sheet follows the sheet, andpresentation="popover"keeps the released menu without the lift (architecture:public-component-apiINV16). - FR34 — A sub-menu drills in under a finger. Under a finger on a
compact touch screen, an
adaptivesub-menu row MUST drill in: the sub-menu's rows and a leading "Back to" row replace the menu's rows in the same surface, no flyout opens, and Back returns to the row that opened it ( component:DropdownMenuFR11 and FR20). The change between levels plays on the theme's move duration and easing tokens (FR45); under reduced motion FR8 applies. - FR35 — A presentation takes no input while it enters. Under a finger, a
tap or a drag that lands while a touch presentation is still entering, a
Popover or an anchored menu growing out of its trigger, an alert
(
component:AlertDialog), a sheet, a dialog, a Drawer, MobileNav, or Lightbox, MUST NOT close it, scroll the page, move focus, or reach anything beneath it; the presentation finishes entering and stays open. Around a non-modal sheet only a tap or a drag on the sheet is held; the page stays live (component:BottomSheetFR11,component:BottomSheetSwitcherFR5). Only pointer input is held: keys and assistive technology stay live, and the content stays in the accessibility tree. A pinch still zooms the page (FR10). During an entrance this rule applies instead of FR6's catch: the entrance finishes first. A mouse keeps today's behavior (DEC-16).
Release decisions¶
- FR36 — One decision, at the release. A drag that can commit an action
MUST decide once, when the finger lifts: if its projected travel (the
travel so far plus the release velocity times the use's projection, FR3)
reaches the use's commit point, the action commits; otherwise the surface
springs back. The decision MUST NOT change while the surface settles. The
same rule backs dismissing a BottomSheet, a Toast or a Lightbox, popping a
NavigationStack, and dismissing the keyboard; each use's commit point and
projection are measured values (FR1, FR2). A BottomSheet's touch release takes
UIKit's measured sheet values. Its projection is 0.1 s of the release
velocity, and its commit point is halfway from its lowest detent to closed. A
release past its measured flick speed lands on the first position at or past
its projection, at least its next one. So a short fast flick at its lowest
detent closes it (
component:BottomSheetFR19). When the owner refuses the close and opens a confirmation dialog in answer, the sheet waits at a peek until the dialog closes instead of springing back (component:BottomSheetFR21). A row swipe keepsspec:AST-057's own release rule. - FR37 — Moving back cancels. A release whose velocity points back toward the start MUST cancel, whatever the travel so far.
- FR38 — The settle continues the pointer. The commit or the spring-back
MUST start at the release velocity (FR6), under every pointer (FR43), on a
spring whose duration the theme's
temposcales and whose measured bounce itscharacteroffsets by the role's fixed weight (FR45). Under reduced motion it followsdesign:reduced-motionDR2, and a release from a mouse, a trackpad or a pen follows FR43. - FR39 — The action never needs a drag. Every action a drag commits MUST
also be reachable without a drag, by keyboard and by mouse
(
architecture:interaction-modalityINV4). - FR40 — Release velocity. The velocity FR36–FR38 read is governed by
spec:AST-100.
Text selection¶
- FR41 — A held finger does what the hold does, not a selection. A tap
activates as it does today and never selects text. On an element whose hold
does something, such as a ContextMenu trigger or a row with a context menu
(a long press at FR12's threshold), or a control whose own record defines a
hold action, such as a slider's thumb or a stepper's hold-repeat, the hold
does that and the browser's text-selection start and callout are suppressed
for that press only, lifted at the lift or a cancel; that element's text is
not selectable by a long press, and Astryx adds no Copy item to a menu. An
element's existing always-on suppression stays as it is. On a label or plain
text whose hold does nothing, such as a checkbox row's label, a long press
selects natively, with the browser's handles; any other element follows its
own record.
A finger held on a control's own box (its non-text part) starts no text selection; lifting it activates the control as a tap does. Text beside it keeps native selection.
Keyboard and assistive-technology selection are unchanged. A pen's hold
acts as a finger's; a mouse makes the context request by a right click, not
a long press (FR43), and otherwise keeps its released behavior
(
spec:AST-017FR59; DEC-9). A mouse or pen drag that a recognizer claims takes no new text selection for that drag and never clears an existing selection; a drag that starts on selectable text is not claimed. An unclaimed mouse drag keeps its released behavior.
Guidance: a caller whose menu element carries text a person may want offers a Copy action in its menu.
Haptics¶
- FR23 — Haptics where the native counterpart plays them. A touch
presentation MUST play a haptic only at the moments its UIKit counterpart
does. In iOS Safari the only haptic a page can produce is a light impact from
a real tap landing on a
<label>or a switch checkbox; a moment UIKit marks mid-drag or after the lift has no haptic there, and the component records that gap.navigator.vibratestands in where the platform offers it.
Resources and compatibility¶
- FR24 — Gesture work costs nothing where it is not used. A component
that uses no gesture registers no gesture listener, observer or timer, and
while a touch presentation is disabled none is active. Under a fine pointer
a component that uses a gesture listens only on its own element and adds
document listeners only during a press, removing them at the release (FR43);
the shared press controller and the menu press model's stray-click
swallower (
module:DropdownMenu/useMenuPressPR2), each installed once per page, count once and not per component, an action group's release-armed click swallower (FR19) counts as press work, and a claiming recognizer'stouchmovelistener for a finger (FR19) counts outside this budget. The number ofdocument- orwindow-level touch listeners MUST NOT grow with the number of component instances, a repeated row or cell adds no touch observer of its own, and nothing touch-related remains after the last instance unmounts (architecture:react-component-runtimeINV5, INV7). -
FR25 — A moved default keeps a way back. Where a touch presentation moves a released default, the way back and its release note are governed by
architecture:public-component-apiINV16 andspec:AST-017DEC-23 and FR3. This record moves four: Selector'sadaptivepresentation policy; DropdownMenu's omittedpresentation, released as'popover', whichpresentation="popover"keeps (FR29); ContextMenu's omittedpresentation, released as'popover', whichpresentation="popover"keeps without the lift (FR33); andmodule:DropdownMenu/useMenuPress's released 500 mslongPressDelayMs, which a caller keeps by passing it (FR29). This replacescomponent:SelectorDEC-1's width-and-pointer query with the FR13 rule foradaptive. -
FR42 — The default look grows no box for touch. The default Astryx look makes no box size increase for phones or touch: row heights, control sizes and target sizes stay as they are; a box may shrink to fit a compact screen, such as an alert's phone width. Type sizing is outside this rule, including a box that grows only with its text, such as a Button whose label follows the 16 px reading base: the 16 px mobile reading base (
design:mobile-typographyDR1, DR3) and the 16 px text-entry floor (family:input-fieldsFR9) are unaffected. Under a coarse pointer, the touch target grows toward 44 × 44 px, up to halfway to a neighboring target, and is never smaller than the control's own box (owner decision, 2026-11-04;spec:AST-094FR42). It grows through an invisible hit area. A hit-area expansion never overlaps a neighboring interactive element's own target: where neighbors are closer than 44 px, the expansion is clamped to half the gap, or skipped, so each element stays reachable; an expansion a component or module record sets on purpose, such ascomponent:ThumbnailAR4's, is unaffected. Mobile size increases belong to theme adaptations (DEC-20). - FR43 — Gestures work on the web. Gestures attach for every pointer, a
mouse, a pen, and a finger, not only a coarse primary pointer. A part that
follows a pointer's drag, such as a switch's or a slider's thumb, a sheet, a
pager, a picker wheel or a row, follows a mouse, a pen, a trackpad and a
finger alike, with the same rubber band past its ends, wherever its record
lets that pointer drag it, and a release from any of them settles on FR45's
spring from the release velocity. These stay
off: row swipe actions under a mouse drag, which would take the browser's text
selection and native drag, while a trackpad's horizontal scroll swipes a
row (
spec:AST-057AR2, DEC-7); a pinch under a pen; the screen-edge pan under a mouse, a trackpad, or a pen; the slide across an action group under a mouse, and under any pointer outside the touch presentation (family:action-groupsFR1); and the 44 px coarse-pointer touch target, which stays coarse-only and never overlaps a neighbor's target. On the web, a pan takes a trackpad's two-finger scroll where its record allows it, and never a mouse wheel's notches. A scroll is a trackpad's only when it carries Chromium's and WebKit's trackpad signature: pixel deltas whosewheelDeltais three times the delta, with no whole tick (awheelDeltathat is a multiple of 120 over a delta that is a multiple of 40 px) and no accelerated-mouse remainder (a fractional part under 0.01 px). Any other scroll, Shift+wheel and a tilt wheel included, is a mouse wheel's, and a mouse wheel scrolls what is under it. A thumb that sets a value, a slider's or a switch's where it pans, takes neither, so a scroll over it goes to the scroll under it (DEC-23). The web reports no trackpad contact or phase, so one splitter reads every trackpad stream (DEC-24): while the fingers move, a pause of 180 ms on a vertical pan or 220 ms on a horizontal one ends the gesture; the fingers' lift is read at the fourth or later delta of a shrinking run, once the run has lost a fifth of its size; momentum after the lift never moves a surface or continues a gesture; and during momentum a reversal, a delta that rises against the decay, or a 50 ms gap starts a new gesture without a pointer move; a late, coalesced wheel event that continues the glide's deceleration belongs to the same flick. While the splitter has not yet decided between a lift and fingers still moving, the surface keeps moving at the fingers' last speed, never farther than that speed carries it over the held deltas; a lift then continues without a stop, and fingers that keep moving take up the difference. A pan released at the lift releases with the fingers' last velocity (FR36); a pan whose stream stops releases still. A window blur or a hidden page cancels a trackpad pan, as the browser taking a touch cancels a finger's. A pinch takes a ctrl-wheel and ends 100 ms after its last event. A BottomSheet's pull follows a trackpad as it follows a finger: a sheet a swipe cannot close (purposeformorrequired) stretches past its resting place on FR3's rubber band for a finger and a trackpad alike, the same travel giving the same stretch, a trackpad's pull reaching no farther than the sheet's height, and springs back at the release; aninfosheet closes on a flick or past its close distance and otherwise springs back (FR36, FR37), and a close its owner refuses rests ascomponent:BottomSheetFR21 states; a mouse wheel never moves a sheet. A pager follows a trackpad swipe, never more than one page from where the swipe began, rubber-banded at its first and last page; it commits past half a page or on a flick, never on a speed spike that moved it less than a tenth of a page, and a swipe that lands during a settle starts from that settle's page, so back-to-back swipes page on. A swipe row follows a trackpad swipe from its first event past its 8 px start and settles at the release to the nearest detent by position and velocity, and a long fast swipe fires the outermost action wherespec:AST-057allows a full swipe; within one gesture an open row only closes, never passing rest to its other side. Every followed trackpad pan runs one shared path (the splitter, the pan, the snap-point drag and the animator), and a component declares only its detents and actions, a row's beingspec:AST-057's. One shared context request module,gestures/contextRequest.ts, answers a finger's or a pen's long press, a right click, and Shift+F10 or the context-menu key. It makes one request per gesture, names the input that made it, and keeps the browser's own menu closed. A hold loses to a claim another recognizer made first. The headless context menu (spec:AST-107FR8) makes its request through it, and ContextMenu through that menu (component:ContextMenuFR10). One module keeps these rules the same in every menu. The press model has a fine-pointer profile with no delay (FR11); and with a mouse, a trackpad, or a pen where the primary pointer is fine a reorder starts on a drag from its handle without a hold, while a pen where the primary pointer is coarse keeps the finger's hold (spec:AST-103FR3). Under a fine pointer only a component that uses a gesture listens (FR24), and under reduced motion a release from a mouse, a trackpad, or a pen followsdesign:reduced-motionDR2 on a coarse primary pointer and DR3 otherwise; and gestures add no stylesheet bytes (DEC-21).
Platform support¶
- Supported engines: Astryx's supported browsers (
spec:AST-013) with touch input, on iOS and Android, and, for FR43, desktop browsers with a mouse, a trackpad, or a pen. A trackpad drives a pan only in a browser that reportswheelDelta(Chromium and WebKit); elsewhere every scroll counts as a mouse wheel's (FR43). UIKit on the reference release is the parity reference, not a support floor; an older iOS Safari gets the same behavior wherever its engine supports it, and Android Chrome gets the same behavior. This amendsspec:AST-013FR3 with an explicit Android Chrome support row for touch presentations. - Unsupported behavior: haptics outside the moments FR23 allows. Where an engine cannot run a curve on its compositor, the animation still plays and still ends on its committed state.
- Browser evidence: the busy-main-thread proof and no layout or paint during
the animation in Chromium with phone emulation, the busy-main-thread proof
in WebKit, curves sampled by seeking the running animations, iOS simulator
recordings for every claim about the reference values, real-device evidence
for every claim about iOS Safari behavior, and, for every claim about
Android Chrome behavior, Chrome with Gboard in the Android emulator at the
exact head, or carried to it under DEC-31, with animations at normal scale
and removed, plus a slow-device profile, with no human device check
(
spec:AST-013FR10, DEC-27, DEC-31). - Presented hit testing (FR11's and FR19's iOS WebKit sentences): unit tests that mimic iOS WebKit's hit testing at the motion's start, the WebKit tap and drag proof with the correction off as its control, and the iOS Simulator gate a merge; real-device evidence for it follows merge.
Current-state impact¶
architecture:theme-tokensandarchitecture:theme-authoring-contract: the three motion knobs join the motion configuration (FR4, DEC-15,spec:AST-108).architecture:interaction-modality: the touch-presentation conditions (FR13) sit beside the shared modality state, and INV13 gives every action group one press tracking (DEC-17).architecture:react-component-runtime: FR24 states the caller-visible outcome of INV5 and INV7 for touch work; both are unchanged.- Under FR41: ContextMenu's trigger, DropdownMenu's built-in trigger and its menu, and Slider's track already turn selection off at all times (the menus also the callout), and that stays. A held finger on other rows and controls with a hold action can start a selection or the callout today, and no shared, press-scoped suppression exists.
family:buttons: the control and cell press profiles (FR11).- Each overlay member's own record (Dialog, BottomSheet, Drawer, Popover, the
menus): its touch exit and its Reduce Motion cross-fade (FR7, FR8), since
members own their animation (
family:overlay-dismissalAV6). design:reduced-motionowns the reduced-motion rule FR8 applies.component:SelectorDEC-1:adaptiveresolves through the FR13 touch rule (a coarse pointer and thespec:AST-012FR9 compact definition) instead of its own width-and-pointer query, withpresentationas the way back (FR25).component:DropdownMenuandcomponent:ContextMenu: an omittedpresentation, released as'popover', follows FR29 and FR33 under a finger;presentation="popover"keeps the released behavior (FR25).module:DropdownMenu/useMenuPress: the released 500 mslongPressDelayMsdefault gives way to FR29's timing; a caller that passes it keeps it (FR25).module:DropdownMenu/useMenuPress: its finger and pen rules (FR1–FR3, FR6, FR7, FR9, FR11) follow FR26–FR30, FR33, and FR11's profiles under every primary pointer; its mouse rules (the mouse halves of FR1–FR3) and its non-gesture rules stay in the module.spec:AST-057: a trackpad's horizontal scroll swipes a row (DEC-7), following the fingers and settling to the nearest detent (FR43); a mouse drag and a mouse wheel never do.component:BottomSheet: aformorrequiredsheet rubber-bands past its resting place under a finger as under a trackpad (FR3, FR43), with the same stretch for the same travel; a mouse wheel scrolls its content and never moves it. Past its tallest detent, every finger's pull stretches it on FR3's rubber band with no hold, over a reserve deep enough for the whole stretch and the release, unless the caller sizes or styles it (component:BottomSheetFR18). A pull on its content does so once the content cannot scroll that way (component:BottomSheetFR18). Past its tallest detent, a mouse and a pen keep FR18's resisted stretch of at most 48 px, an exception to FR43's same rubber band (spec:AST-017FR59). Implementation gap: a finger drags it one for one below rest.- The shared pager (Carousel's paging presentation, Lightbox's viewer): a
trackpad swipe follows FR43's pager rule in Lightbox's viewer and in
Carousel's paging presentation, under every pointer (
component:LightboxFR11). - The shared pager's loop arithmetic:
hooks/usePager.tsexportsmodandnearestLoopCopy, and DateInput's looping picker wheel imports both (component:DateInputDEC-3). architecture:react-component-runtimeINV13: gestures attach for every pointer, within FR24's listener budget.design:user-statesDR1, DR3 andfamily:buttons: press timing follows FR11's profiles under every pointer, the fine-pointer profile included.- Every
family:action-groupsmember outside the menu press model: a press that slides across sibling actions acts on the action it lifts on (FR26–FR28), under the touch presentation (family:action-groupsFR1). - Every component under a coarse pointer: no box grows for touch, and a touch target reaches 44 px only through an invisible hit area clamped by its neighbors, unless a component or module record sets its own (FR42).
component:DropdownMenu,component:ContextMenuandcomponent:Popover: under a finger they follow FR26–FR35 as each applies. Popover's input hold (FR35) starts on the first frame after the open, so a touch that lands within that frame reaches the page.component:AlertDialog,component:Dialog,component:BottomSheet,component:BottomSheetSwitcher,component:Drawer,component:MobileNavandcomponent:Lightbox: under a finger, a tap or a drag during the entrance is held (FR35), an exception during the entrance tocomponent:BottomSheetFR7,component:BottomSheetSwitcherFR6,component:PopoverDEC-8 (a Popover presented as a sheet),component:MobileNavFR4 andfamily:overlay-dismissalAV4, which otherwise let a scrim or overlay tap close at any time (spec:AST-003FR10 andarchitecture:layer-runtimeINV14 leave dismissal to the component). Toast and a non-modal sheet (component:BottomSheetSwitcherFR5 and its Non-modal state) do not hold the page: the page behind them stays live, and only the sheet itself holds a tap or a drag while it enters. Dialog, Drawer, MobileNav and DropdownMenu hold an entrance only under a coarse primary pointer: where the primary pointer is fine and the screen also takes touch (a touchscreen laptop), a finger's tap or drag during the entrance is not held. After a finger, the first press of a mouse that has not moved since passes the entering presentation's shield where the page last heard the mouse. The shield reads that point when it comes up, and again at each press or move of a finger or a pen. A shield over the viewport opens for a mouse only at the point last read, and not at all if the page had heard no mouse by then. It also opens where each finger or pen that was already down when it came up rests, and that opening follows the press until it lifts. A still mouse resting anywhere else presses the shield, and its press does nothing. A non-modal Drawer shields only its panel, and that shield stops a mouse only if the page had heard none at the last read. A move of the mouse lowers the shield first.- BottomSheet, Toast, Lightbox, NavigationStack and keyboard dismissal: a drag that commits follows FR36–FR40.
spec:AST-100owns release velocity, which FR17 reads.- Under FR45, motion that a tap, a hold, a key or the program starts plays the
theme's duration and easing tokens in a tap component, and the component's
springs from rest in a gesture component, under a finger as under a mouse. The
records that state such motion carry it: on tokens,
component:DropdownMenuFR21,component:PopoverFR9,component:AlertDialogFR6,component:TreeListFR8 andcomponent:ProgressBarFR4; on springs,component:SwitchFR9, FR10 and FR15,component:SegmentedControlFR9 and FR10,component:SliderFR7,component:ContextMenuFR5,component:LightboxFR5, FR12 and FR16 andcomponent:DateInputFR14. A tap component's touch exit that a tap, a key or the program starts playsspec:AST-090's--duration-exitand--ease-exit, and no exit switch removes it (FR7;spec:AST-090FR14 and DEC-5 carry it). On Switch and SegmentedControl, every change under a touch presentation settles on the spring, as it does today; without a touch presentation a click, a key or a change of value keeps the theme's curve, unchanged. Implementation gap: ProgressBar's fill still moves linearly forprogress.fillTrackMstimes the share of the track moved under a coarse pointer (component:ProgressBarFR4). - Under FR45, a swipe row is a gesture component: a close or return that a tap
or Escape starts (
spec:AST-057FR5, FR7) plays the row's spring from rest, and a swipe that closes it keeps its measured spring from the release. - Under FR45, RefreshControl's endRefreshing is the exception: it plays UIKit's measured 300 ms ease-in-out curve from the theme's duration token and UIKit's measured curve, since no spring from rest matches it within tolerance (iOS 26.2 simulator, 2026-11-07). The curve follows the theme's tempo through the duration token, so a slower theme still slows it.
- Under FR45,
spec:AST-107'ssettleToand ananimatecall without a velocity play a spring for motion that no gesture drives. Their records keep their springs until each carries FR45. - Under FR43 and FR45, a part that follows a pointer follows every pointer
and its release springs from the release velocity under every pointer:
component:SwitchFR15's thumb under a mouse or a pen,component:SliderFR7's coast after a mouse or a pen release,component:SegmentedControlFR10's settle after a mouse or a pen release, andcomponent:DateInputFR15's wheel under a trackpad wherever the sheet shows. Implementation gap: Switch's thumb does not follow a mouse or a pen, Slider's mouse and pen releases do not coast, SegmentedControl's mouse and pen releases slide on the theme's duration, and DateInput's wheel takes a trackpad only under a coarse primary pointer. design:user-statesDR1 and DR3,spec:AST-025FR14 andspec:AST-013FR3 each carry an amendment for touch presentations (FR11, FR14, Platform support);design:motionDR3 and DR5 (draft) are departed from or met as FR4 and FR8 state.- FR6 gap: a retarget made inside a page's own frame or ResizeObserver callback shows its new curve one frame later.
- FR6 gap: under a starved compositor, Chromium can show a frame 40 to 60 ms after the main-thread frame that builds it. A retarget then first shows that far into its curve: up to 6.5 px on a loaded Switch.
- FR6 gap: a resize during a settle drops its velocity when it leaves the row past its new last page, or when the settle began before the viewport had a width. The row lands on its target at once.
- Consumer docs: none until a component ships its touch presentation; each
component documents its own, including the
presentationvalue that keeps the released surface (FR25).
Motion that FR45 moves, by component. Each component's record carries its own line, except Carousel, whose trackpad paging this record states through the shared pager (FR43):
| Component | Motion | Today | Under FR45 |
|---|---|---|---|
| Switch | Thumb travel and track colour on a tap, a hold, a click or a key under a touch presentation | Measured switch springs | The thumb's switchControl.travel spring from rest |
| Switch | Thumb travel and track colour on a click, a key or a value change without a touch presentation | The theme's curve (--duration-fast, --ease-standard) |
Unchanged: the theme's curve |
| Switch | Thumb lift while a finger presses, with a minimum lift time | Measured lift and settle springs | switchControl.lift (gesture component) |
| Switch | A mouse's or a pen's drag | Thumb still until the release, then the theme's duration | Thumb follows; the release springs from its velocity |
| Slider | Thumb lift and drop under a finger | Measured lift and drop springs | springs.sliderLift and springs.sliderDrop (gesture component) |
| Slider | A mouse's or a pen's flick | Ends at the release | Coasts and settles as a finger's does |
| DropdownMenu, Popover | Grow from the trigger and shrink back under a finger | springs.menuOpen, springs.menuClose |
Theme entrance tokens; theme exit duration and easing |
| DropdownMenu | Sub-menu drill-in on a compact touch screen | springs.subMenuOpen, springs.subMenuBack |
Theme move tokens |
| ContextMenu | Trigger lift and the menu's grow after a long press | springs.contextMenuLift, springs.contextMenuMorph |
The same springs (gesture component) |
| AlertDialog | Scale-in present under a finger | springs.alertPresent |
Theme entrance tokens |
| Lightbox | Controls fade on a tap, a double tap's zoom, the grow from its source | Named measured roles | Springs, springs.settle unless the motion table names another role; the controls fade keeps the main spring's pace |
| TreeList | Group slide under a coarse pointer | Measured motion | Theme tokens |
| ProgressBar | Determinate fill on a value change under a coarse pointer | Linear, progress.fillTrackMs times the share moved |
--duration-medium and the theme's easing, every pointer |
| DateInput | Sheet wheel under a trackpad | Coarse primary pointer only | Wherever the sheet shows |
| Carousel | Paging under a trackpad swipe | Coarse primary pointer only | Every pointer |
| Every tap-component overlay | A touch exit that a tap, a key or an outside press starts | The native counterpart's timing | --duration-exit and --ease-exit; the exit switches never remove it; a gesture component's such exit, such as a sheet's or the Lightbox's, plays its spring (FR7) |
| SegmentedControl | Selection slide on a tap, a click or a key under a touch presentation | segmented.selectionSpring |
The selection spring from rest (gesture component under touch) |
| SegmentedControl | Selection slide on a click, a key or a program change without a touch presentation | The theme's duration and easing | Unchanged: the theme's curve |
| SegmentedControl | A mouse's or a pen's drag release | Slides on the theme's duration | Settles on a spring from the release velocity |
Verification¶
| Contract | Verification | Representative states | Mutation or failure expectation |
|---|---|---|---|
| FR1, FR2 | Value check over every measured value and its uses | every value; a guess and its measurement task; a platform-specific value; two components playing the same motion | an unsourced value, an unknown source kind, a guess without a listed measurement, an unsourced platform split, or two values for one use fails |
| FR3 | Unit tests of the spring, decay, rubber band and projection math against an independent integration and values read from UIKit | under-, critically and overdamped springs; release velocities; both rates; overscroll depths | changing a formula or a constant breaks the agreement with UIKit's values |
| FR3 pager | Unit tests of the pager's page choice against the recorded UIKit releases | releases at 292.7–298.6 pt/s that stay and 310.7–329.9 pt/s that advance, at 10, 25 and 40 % of a page; releases at rest at 45–48.5 % and 55–57.5 %; a 1.5-page drag released at 0, 600 and 3000 pt/s; a release moving back toward the start page | a page chosen by projection, a release at or past 300 pt/s that stays, or a release that travels more than one page from its start fails |
| FR4 | Role unit tests over every touch motion | each role at its table value; a theme that writes motion |
a literal played in place of a role (other than a measured gesture-driven exit spring its component's motion table lists with its platform source), a value that differs from the table at tempo 1 and 'standard', or a theme that changes a role other than through its motion knobs fails |
| FR4 | Role unit tests over gesture-driven exits | a gesture-driven exit (a release that closes or dismisses) playing a spring measured from the platform reference with no named role; the same unnamed spring played by a program-started motion or by a gesture-driven motion that is not an exit, such as a settle | a gesture-driven exit playing a measured table spring passes; a program-started motion, or a non-exit gesture motion, playing an unnamed spring fails |
| FR5 | Browser proof: an animation keeps advancing frame by frame through a 1 s main-thread block, with no layout or paint per frame; a frame interval counts as a miss only when the animation's own curve moves at least one capture step since the last frame that showed a new position | Chromium phone emulation; WebKit | a script-driven or layout-animating implementation freezes or lays out |
| FR5 glide | Browser proof: the animated-layout glide keeps moving through a 700 ms main-thread block, on every frame a compositor control moves | the content after a Collapsible, a TreeList branch and a Table row; verified in Chromium; WebKit by an iOS Simulator spot-check (38/39 frames), not an automated run (evidence gap) | a glide stepped from the main thread freezes |
| FR6 | Unit and browser tests catching an animation mid-flight and retargeting it | catch at peak velocity; retarget with a new spring; a retarget before the browser reports the call's start | a layout read, a jump, or a lost velocity fails |
| FR6 pager | Unit and browser tests of a pager's settle start | releases just under and over 225 pt/s; a catch mid-settle; a programmatic page change mid-settle | a release under the floor whose settle starts moving, a release over it whose settle starts from rest, a catch that loses the on-screen velocity, or a programmatic page change mid-settle that starts from rest fails; a page change during a drag starts from rest |
| FR6 starved | Switch frame proofs on a starved main thread (4 workers on 2 cores); unit tests of a retarget on a settle tail and a rebase toward a new rest | a second tap mid-travel, with frames read late or its lift handled 100 ms late; a first frame committed late; a retarget once the thumb is still; a value change mid-slide, whose rebase moves the travel whole | a jump out of a thumb that is still fails; a value change mid-slide shows no step |
| FR6 late commit | A browser test of a retarget behind a 200 ms block; unit tests of a retarget whose frame comes late | a retarget made in a task, and one made in a frame callback of the page, before a 200 ms block; a frame within 34 ms of the call; a velocity the call hands the spring; a hidden page; two properties, and two animators, before one late frame; retargets on two animators in one callback | a step at the frame that commits a retarget fails; a retarget whose frame comes within 34 ms keeps the call's own clock; a retarget made in a frame callback of the page that shows its new curve in any frame but the next fails; a late frame that drops a handed velocity fails; a hidden page's retarget that never finishes fails; a later call before a late frame that keeps its own clock fails; two animators' retargets in one callback on different clocks fail |
| FR6 resize | Unit and browser tests of a resize during a pager's settle | a narrowing that renumbers the pages mid-settle; a widening and a narrowing of pages as wide as the row, mid-settle and mid-drag; a rotation of pages with a fixed gap; pages that share a shift; a still finger whose catch spans a resize; a widening that regroups fixed-width views; a tie between two pages (units); a narrowing that splits the last page from the stop before it; a narrowing while a release settles toward the last page, sampled every frame on each settle's own clock; a settle begun before the viewport had a width, which lands on its target at once | a settle that ends on its old index's new offset, a settle or release on scaled pages that ends on another page or loses its fraction of a page, a regrouping that jumps, a tie that reverses, a settle toward the last page that ends short of the new last page, a split-end settle that rests on the split-off stop, or a frame after that narrowing more than 1 px from the paging integrator's curve fails. The curve runs from where the settle shows as the new one starts, at its velocity then, to the new last page. The first frame after the narrowing may still show the settle before it, or the new curve between its start and its clock, where the browser commits it inside that frame |
| FR7, FR8 | Component browser tests and storyboards with and without Reduce Motion | entrance, exit, move; a drag and its lift under Reduce Motion; a tap-, key- and program-started close of a sheet and the Lightbox | 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), an opacity fade over 200 ms, or a tap-, key- or program-started close of a gesture component on the exit curve instead of its spring, fails |
| FR45 | Browser tests with a mouse, a pen, a trackpad and a finger at each tempo bound and each character, and with Reduce Motion |
a tap, a click, a key and a programmatic change on a Switch, a menu, an alert, a sheet and a ProgressBar under a fine and a coarse pointer; a drag release, a flick and a pinch on a Switch, a Slider, a sheet, a pager and a Lightbox photo under each pointer; a tap that continues as a drag | a tap, click, key or programmatic change in a tap-classified component that plays a measured role or a spring instead of the theme's duration and easing tokens, a touch tap-started move in a gesture or gesture-capable component on a curve instead of its spring, a click, a key or a value change on Switch or SegmentedControl without a touch presentation that leaves the theme's curve, a velocity-carrying release that settles from rest or on a curve, a gesture's spring that ignores character or tempo, or a part that follows one pointer and not another, fails; the pager's measured settle, which does not yet follow character, is a recorded implementation gap |
| FR45 | Component source and token tests for a tap component's motion whose record names no step, with a platform measurement | a small anchored surface (a popover, a menu, a toggle, a row) and a full-screen surface (a Dialog, an AlertDialog), each with its own measurement; a tap component's overlay exit | a token cited as nearest to the measurement in the Storybook theme passes, and a tap component's overlay exit on --duration-exit passes; a token chosen by role alone, or nearest at Core's unthemed defaults, fails |
| FR45 | Browser frame capture of companion motion in a gesture and a tap component | a sheet's scrim, handle and content fade; a Lightbox's chrome fade; a menu's backdrop | a companion fade on its own duration fails; one driven by the main motion's progress or settle time passes |
| FR45 | Browser frame trace of RefreshControl's end at tempo 1 and at each tempo bound, and a unit test of the end's timing |
a refresh that ends with its indicator shown, at tempo 1 (300 ms), 0.75 (225 ms) and 1.5 (450 ms); a theme whose move easing differs from UIKit's curve |
an end whose per-frame trace leaves UIKit's measured 300 ms ease-in-out by more than 0.75 pt at tempo 1, an end on the theme's move easing instead of UIKit's curve, or a duration that ignores the theme's tempo, fails |
| FR45 swipe row | Browser frame traces of a held swipe row in Chromium and WebKit, read against each touch move | a 140 px drag over 0.4 s, held 0.6 s; a slow drag from the open row to 40 px past the confirm point, held 0.6 s | Short of the confirm point, a frame from the claim to the lift whose row travel differs from the finger's travel since touch-down by more than 1 px fails; past it, a lead that shrinks, or that ends away from the confirmation offset, 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; a press on a row of a menu whose rows fit and of one that scrolls; a slide-off lift on a Switch and on a Radio | the wrong profile's timing, a press that survives the browser taking the touch, or a control outside an action group activated other than by the browser's click, outside spec:AST-020 FR9's slide-off exception, a row of a menu whose rows fit that waits 150 ms, or one of a scrolling menu that does not, or a slide-off lift that completes a control outside spec:AST-020 FR9's exception, fails |
| FR11 theme | generateThemeRules.test.ts themed-:active cases; real-browser forced :active on the Themed press story |
a theme :active on a base and on a variant with a trailing pseudo; fine pointer; coarse pointer with forced :active and with the press attribute |
a bare theme :active rule a coarse pointer matches, or a coarse arm keyed on :active, 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 |
| FR18–FR22 | Browser tests with real touch input (spec:AST-013 FR10) |
per-axis pans beside native scrolling, page zoom, cancelled touches, clicks after taps, keyboard activation, a modal scroll lock, a control that keeps its press through a drag; a still finger with sub-pixel jitter over a scroll view; a finger moved 9 px and 10 px straight, and (7, 7) and (8, 8) diagonally; a recognizer on an element whose author touch-action is narrower, including one without pinch-zoom; a screen-edge pan landing at 40 px and at 41 px from the edge, at 14 px and 15 px of travel, and a horizontal scroll that starts outside the band; a screen-edge pan on an element within the band, and on one that reaches beyond it; a sheet's pull from a list at its top, and from a list scrolled away from its top; a long press dragged past its tolerance after it began, which never scrolls the page |
a ghost click, a scroll or zoom blocked other than by the author's touch-action, or a cancelled unowned touchmove outside FR19's five exceptions, a tap cancelled by sub-pixel movement or by under 10 px of travel, a scroll that does not take the touch at 10 px, or a derived touch-action wider than the author's, a screen-edge pan that claims outside its band or before 15 px on an element within the band, or has not claimed at 15 px, or an author scroll outside the band that is blocked, a band claim of pan-x on an element that reaches beyond the band, or a 15 px start there, or a scroll-edge pan that cancels a move a scroller could scroll, or begins before 10 pt, fails |
| FR19 (DEC-30) | Gesture unit tests on synthetic streams; browser tests with real touch input in WebKit and Chromium | a tap that wobbles 2–4 px toward a scroll edge keeps every move, and a 5 px move is cancelled; a sideways move is never held; NavigationStack's content back swipe on a pushed screen; RefreshControl's pull at its top, whose touch path is not a scroll-edge pan (a guard) | a move under 5 px along the pan's axis cancelled, a move from 5 px left uncancelled while every scroller under the finger sits at its edge, a sideways move held, or a pan that begins before its hysteresis fails |
| FR20 | Browser tests with real touch input in Chromium phone emulation (spec:AST-013 FR10) |
a horizontal drag under pan-y; a vertical drag under pan-y over a scroller with room; a vertical drag where no scroller has room |
a horizontal drag under pan-y counted as the browser taking the touch, a vertical one over a scroller with room not counted, or a later uncancelable move counted, fails |
| FR23 | Haptics tests on the recorded moments | tap, drag, lift | a haptic outside a native moment fails |
| FR24 | Resource tests counting listeners, observers and timers | fine primary pointer; coarse pointer enabled and disabled; many instances; unmount | a gesture listener in a component that uses no gesture, an idle document listener outside a press other than the one shared press controller and the one stray-click swallower, a second press controller, a per-instance document or window listener, or a leak fails |
| FR25 | Component tests of each moved default and its presentation value |
default; presentation set to the released surface |
a moved default that presentation does not restore, or a public threshold, fails |
| FR26–FR28, FR30 | Menu press tests and each member's pointer-stream tests, as family:action-groups' verification map lists them and a real-Chromium touch test |
a slide from one row to another; a lift outside; a cancel; a second finger; edge autoscroll | an act on the press-start row, two acts for one gesture, a lift outside that closes, or a lit row after a cancel fails |
| FR29 | Trigger tests with explicit timestamps | a press in a fixed bar; a press in scrolling content held 149 and 150 ms; a quick tap in scrolling content; a scroll taking the touch before 150 ms; a drift of 12 and 14 pt; moves before and after the handoff; presentation="popover" |
a fixed-bar press that waits, a held finger's scroll-view open before 150 ms or after a scroll, a quick tap that does not open at its lift, an open past the drift allowance, a lift that acts before the handoff, or a popover trigger that opens on press fails |
| FR31–FR33 | Browser tests and storyboards under a finger | a menu, a Popover and a ContextMenu lift: open, close, a pan outside, a tap outside, a pinch over the surface; a mouse | a surface that does not grow from and shrink into its trigger, a pan outside that leaves a menu open, a Popover whose dismissal changed, a pinch blocked other than by the author's touch-action, a tap outside that reaches the page, or a changed mouse path fails |
| FR34, FR35 | Browser tests and storyboards under a finger | a sub-menu drilling in and its Back row returning; a tap and a drag during a popover's and a menu's growth; a pinch during growth; a mouse; a tap and a drag during an alert's, a sheet's, and a dialog's entrance; a key and a screen reader during an entrance; a pinch during an alert's and a sheet's entrance; a tap and a scroll on the page beside an entering non-modal sheet, which pass | a drill-in that leaves the parent's rows in place, a change between levels that does not play on the theme's move duration and easing tokens, a tap during growth that closes, scrolls or moves focus, a pinch blocked other than by the author's touch-action, or a changed mouse path, a held key or assistive-technology activation, a hidden content tree, or a tap or drag during an entrance that closes the presentation, scrolls a held page, moves focus or reaches anything beneath, fails |
| FR36–FR40 | Release tests on synthetic touch streams with explicit timestamps, per use | below and past each commit point; a flick that projects past it; a slow drag past it; a release moving back; Reduce Motion; keyboard and mouse paths | a decision that changes mid-settle, a release moving back that commits, a settle that does not start at the release velocity (a paging release starts its settle per FR6's paging paragraph, DEC-25), or an action with no keyboard or mouse path fails |
| FR41 | Browser tests with real touch input (spec:AST-013 FR10) |
a tap; a long press on a ContextMenu trigger, a DropdownMenu trigger the caller renders, a row with a context menu, and a slider thumb; a long press on a checkbox row's label and on plain text; a cancelled press; mouse and keyboard selection; a pen long press; a mouse long press, which makes no context request; a mouse drag a recognizer claims, with and without a page selection; a mouse drag that starts on selectable text | a tap that selects, a hold with an action that starts a selection or callout, a label or plain text whose long press does not select natively, a suppression that outlives the press, a change to native selection elsewhere, to keyboard or assistive-technology selection, or to mouse selection outside a drag a recognizer claims, a claimed drag that takes a new selection or after which an existing one does not survive, or a drag starting on text that does not select text fails |
| FR41 (box) | Browser tests with real touch input (spec:AST-013 FR10), and Mobile Safari on an iOS simulator |
a finger held on the box of a checkbox, a CheckboxList row, a radio option and a switch, then lifted still; the same hold on the label beside it; a tap on the box; a hold that moves away; a mouse press on the box | a hold on a box that starts a selection or the callout, a still lift that does not activate the control exactly once, a label whose long press does not select natively, a suppression that outlives the press, or a change to a mouse press fails |
| FR42 | Default-theme geometry tests under a coarse and a fine pointer, and hit-testing between adjacent targets | every component at phone width with a finger and with a mouse; a dense toolbar; a chip and its remove button; a Switch beside a label link | a default-theme box that grows under touch or at phone width other than with its text, or, where no component or module record sets the hit area, a touch target under 44 px where neighbors allow it or a hit area that overlaps a neighbor's target, fails |
| FR43 | Browser tests with a mouse, a trackpad, a pen, a finger, and the keyboard, and resource counts | a pan by drag and by wheel; a slider's thumb under a wheel and a trackpad scroll; a ctrl-wheel pinch; a long press, a right click, and Shift+F10; a mouse press; a handle drag; a row swipe with a mouse and a trackpad; a component with no gesture | a gesture missing under a mouse or pen, a mouse-drag swipe action, a pen pinch, an edge pan under a mouse, a trackpad, or a pen, a press delay under a fine pointer, a wheel or trackpad scroll that changes a thumb's value or does not reach the scroll under it, an idle listener in a component with no gesture, or added stylesheet bytes, fails |
| FR43 trackpad | Unit tests on timed wheel streams; WebKit browser tests with trackpad streams (Chromium's driver wheels read as a mouse wheel) | a form and a required sheet pulled 30 to 240 px by a finger and by a trackpad; mouse lines, notches, ticks and accelerated deltas over a sheet, a pager and a row; ten swipes each starting mid-momentum, ten whose momentum ends, and a slow drag with 150 ms pauses; a trackpad flick and a slow stopped drag on an info sheet; a fling, a slow 60 px swipe, a 42 px spike and back-to-back swipes on a pager; a row opened and swiped back within one gesture, and a long fast swipe; a pinch ending; a trackpad pan through a window blur and through a hidden page | a trackpad stretch that differs from a finger's for the same travel (120 px gives 54 px on the reference sheet), a mouse wheel that moves a sheet, a pager or a row, splitter counts other than ten, ten and one, momentum that moves a surface, a flick released with no velocity, a pager that travels past one page or pages on a spike, an info sheet a flick leaves open or a slow stopped drag closes, an open row that reveals its other side within one gesture, a trackpad pan a window blur or a hidden page leaves mid-gesture, or a pinch that ends after 100 ms fails |
| FR44 | Unit tests of a pen press a window blur ends, on a Switch, a Slider and the host, under a coarse and a fine pointer | a pen press on a Switch and on a Slider, blur mid-press: nothing toggles or commits; a pen whose contact ends in pointercancel |
with the host keeping no note of a blur-cancelled pen, the Switch toggles at the pen's click |
| all | iOS simulator: the UIKit reference capture and the same gesture in Safari; real iOS Safari devices; Android Chrome in the Android emulator (DEC-27) | per component | an unmatched curve or timing is a parity defect |
| all (DEC-31) | The evidence-carry check, before device or emulator evidence from an earlier head counts at a later head | a later head that only merges main; the pull request's own changes byte-identical or changed; a merge that changes a file the pull request changes, a direct import of those changes, a shared motion or layer module, or none of them; a generated file among the pull request's own files that CI proves regenerates identically, or does not prove; a commit, or an overlap with the pull request's own files, confined to test-only files as DEC-31 defines them, or knowledge records, or not |
the evidence-carry check compares the PR's own diff between the two heads, and the merge's changed files against the files the PR changes, the changes' direct imports and the shared motion and layer modules (currently motion/transientCopy, motion/inertClone, motion/animator, motion/carryAnimations, Layer/useLayer, hooks/usePager); any overlap fails, except a generated file among the pull request's own files that CI proves regenerates identically at the new head; a changed own diff, or an overlap with the pull request's own files, confined to test-only files as DEC-31 defines them, knowledge records or .changeset/ release notes, passes |
Decision log¶
DEC-1 — Touch presentations feel native by default¶
Reference: spec:AST-094/DEC-1
Decider: cixzhang, 2026-10-24
Every touch device gets one native-feeling touch behavior by default, without an opt-in, because the people using it already know that behavior from every other app on their phone. The behavior's values are measured from UIKit, not remembered: a number enters the table only with a citable source, and Android touch devices get the same values until a measured, sourced difference is recorded.
The table supplies the defaults and a theme tunes them through its motion knobs (FR4, DEC-15): a product can soften motion without forking a component, and the measured values stay the ones it starts from. Platform-matched look and feel is not part of this decision.
DEC-2 — Recognizers track fingers; the compositor plays releases¶
Reference: spec:AST-094/DEC-2
Decider: cixzhang, 2026-10-24
On iOS, native scroll snapping keeps tracking through a main-thread block, but a finger that lifts during the block finishes on WebKit's own snap physics rather than UIKit's curve, a finger cannot catch the content mid-spring, and full-viewport hit testing breaks surfaces that leave the page usable around them. Tracking therefore runs in the recognizers, and every release runs as a compositor animation of the measured curve (FR5, FR9).
DEC-3 — Touch motion is themeable; gesture thresholds are not¶
Reference: spec:AST-094/DEC-3
Decider: cixzhang, 2026-10-24
A product tunes motion as it tunes color and type, so every touch spring,
duration and curve is a motion role whose default is the measured value and
which a theme reaches through its motion knobs (FR4, DEC-15). Thresholds decide who gets a touch, not how anything looks, so they stay
internal (spec:AST-002 FR3).
DEC-4 — A finger opens a menu on press¶
Reference: spec:AST-094/DEC-4
Decider: cixzhang, 2026-10-24
A trigger in a fixed bar has nothing to scroll, so its menu opens as the
finger presses; inside a scroll view the menu waits out the content-touch
delay so a scroll can still claim the touch (FR29). A caller's presentation
choice keeps today's open on a tap (architecture:public-component-api
INV16).
DEC-5 — FR4 cites the generated motion role table¶
Reference: spec:AST-094/DEC-5
Decider: cixzhang, 2026-10-25
FR4 lists the roles this record names, and cites the generated motion role table, built from every registered table, for the roles a component's own record measures, so a new component table cannot drift from the record.
DEC-6 — CSS keyed on the touch media query counts as after hydration¶
Reference: spec:AST-094/DEC-6
Decider: cixzhang, 2026-10-25
FR13's "only after hydration" governs a presentation decided in script. A style keyed on the literal touch media query conforms: the server and hydrating markup are identical, and the browser applies the style at first paint.
DEC-7 — A watcher recognizer is passive and follows the scroll¶
Reference: spec:AST-094/DEC-7
Decider: cixzhang, 2026-10-25
A recognizer that never claims registers only passive listeners (FR20), so watching a touch never delays the browser's scroll, and it is not cancelled when the browser takes the touch: it follows the scroll to the lift, so a bar that reacts to scrolling keeps hearing it. Nor does a recognizer that claims the touch fail or cancel it: a watcher recognizes alongside the winner.
DEC-8 — A native scroll takes a touch after 10 px; touch-action never widens the author's¶
Reference: spec:AST-094/DEC-8
Decider: cixzhang, 2026-10-25
A still finger often reports sub-pixel movement, and treating that as a scroll
cancels taps the person meant, so a native scroll counts as the browser
taking the touch only once the finger has moved 10 px. An author who narrows
an element's touch-action has a reason, so the value derived from
recognizers is intersected with it and never grants the browser more.
Rejected: cancelling at the first scroll event, and overriding the author's touch-action.
DEC-9 — A hold does its action, not a selection; copying is the caller's menu item¶
Reference: spec:AST-094/DEC-9
Decider: cixzhang, 2026-10-25
Under a finger, a tap, a hold that does something, and a long press on plain text are different intents. A tap activates. A hold on an element whose hold does something (a long-press menu, a stepper's hold-repeat, a slider's thumb) does that without starting a selection or the loupe, as UIKit's context menus and controls and Android's long clicks do. A long press on a label or plain text whose hold does nothing selects natively, so labels stay selectable; other elements follow their own records. Text on a menu element is not selectable by a long press, and the system adds no Copy item, so a caller that wants copying puts a Copy action in its own menu.
Rejected: a system Copy item; suppressing selection on every press-tracked control.
DEC-11 — Touch motion roles stay internal until the public set is decided¶
Reference: spec:AST-094/DEC-11
Decider: cixzhang, 2026-10-25
Motion values stay internal for now: a public, theme-settable set is decided separately, so no component-specific role becomes a public token first.
This defers DEC-1's and DEC-3's theme retuning until that set exists.
Rejected: publishing the per-component roles as theme tokens.
DEC-13 — A screen-edge pan claims only a thin band at the edge¶
Reference: spec:AST-094/DEC-13
Decider: cixzhang, 2026-10-26
An edge swipe, such as going back, starts at the very edge of the screen, and
a page's own horizontal scrolling lives everywhere else. So a screen-edge pan
claims the horizontal axis only in UIKit's edge band and decides there at
UIKit's 15 px, leaving the author's scrolling untouched outside it. On an
element that reaches beyond the band, touch-action cannot claim per touch,
so there an in-band touch decides at 10 px (DEC-22).
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.
DEC-17 — Every group of sibling actions tracks a held pointer the same way¶
Reference: spec:AST-094/DEC-17
Decider: cixzhang, 2026-10-26
A person who presses one action and slides to another expects the same result
in a menu, an alert's buttons, a button group, or a toolbar. Every member
group of sibling actions behaves the same way, decided once and built in
two owners: the menu press model and the action-group tracker
(family:action-groups; architecture:interaction-modality INV13). Menus keep the behavior for every
pointer; an action group's slide runs for a finger and a pen under the touch
presentation (family:action-groups DEC-1). The 44 px target stays
touch-only.
Rejected: a tracking rule for menus only.
DEC-15 — The public motion set is three theme knobs; per-role tables stay internal¶
Reference: spec:AST-094/DEC-15
Decider: cixzhang, 2026-10-26
A theme reaches touch motion only through spec:AST-108's three knobs, tempo,
character, and reduced motion, which transform the measured roles; the
per-role tables and weights stay internal. This supersedes DEC-11's "all
internal" for exactly these three knobs, and DEC-1's and DEC-3's per-role
retuning, which a theme does through the knobs; DEC-11's rejected alternative, public
per-component roles, stays rejected.
DEC-24 — A pan follows a trackpad, never a mouse wheel, and reads the trackpad's phases itself¶
Reference: spec:AST-094/DEC-24
Decider: cixzhang, 2026-10-31
A trackpad's two-finger scroll is direct manipulation, as a finger is, so a pan follows it, and a finger and a trackpad share a surface's rubber band and release. A mouse wheel's notches are a scrolling control, and a few quick notches never move or close a sheet, so a pan takes none, and a scroll without the trackpad signature counts as a wheel's. The web reports no trackpad contact, phase or momentum, and a timeout alone releases under resting fingers, carries momentum into the surface and merges the next swipe, so one splitter infers the lift and the gesture's bounds for every pan. A row follows the fingers, as a mail list's row does. This narrows DEC-21's wheel and trackpad mapping for a pan.
Rejected: a mouse wheel driving a pan; a discrete step per trackpad swipe for rows and paging; a longer end timeout instead of the splitter.
DEC-23 — A thumb that sets a value takes no wheel¶
Reference: spec:AST-094/DEC-23
Decider: vjeux, 2026-10-29
A consistency decision: a thumb that sets a value, a slider's or a switch's
where it pans, takes no wheel or trackpad scroll, so a scroll over it goes to
the scroll under it and never changes the value (FR43). Touch work keeps
released mouse behavior (spec:AST-017 FR59, FR41), and a native range input
ignores the wheel (DEC-1). This narrows DEC-21's wheel and trackpad mapping
for a pan.
Rejected: the thumb's pan taking wheel and trackpad scrolling, as other pans do.
DEC-21 — Gestures work on the web, not only under a finger¶
Reference: spec:AST-094/DEC-21
Decider: cixzhang, 2026-10-26
Most of these gestures work as well with a mouse, a trackpad, or a pen, so
they stay on for every pointer, with web inputs mapped in: wheel and trackpad
scrolling for a pan, a ctrl-wheel for a pinch, and right click or Shift+F10
for a long press. What would fight the browser is off: a mouse drag's swipe
actions, a pen's pinch, and the screen-edge pan under a mouse, a trackpad, or a pen. The 44 px target is
touch-only, and none of this adds stylesheet bytes. A mouse press uses the press model with no delay instead of the
browser's :active. The press controller tracks every pointer.
Rejected: keeping gestures and press tracking touch-only.
DEC-20 — The default look grows nothing for touch¶
Reference: spec:AST-094/DEC-20
Decider: cixzhang, 2026-10-26
Sizes do not grow on phones or under touch in the default look, so a product looks the same everywhere unless its theme chooses otherwise; shrinking to fit a compact screen is fine. Touch reach comes from invisible hit areas, clamped so two close neighbors both stay reachable. Themes own mobile size increases through their adaptations.
Rejected: touch-only row heights and control sizes in the default look.
DEC-16 — Every touch presentation holds pointer input while it enters¶
Reference: spec:AST-094/DEC-16
Decider: cixzhang, 2026-10-26
A tap or a drag that lands while an alert, a sheet, or a dialog is still entering is almost never aimed at it, so it is absorbed, as it already is for a popover or a menu growing out of its trigger. Only pointer input is held, so keyboard and assistive-technology users are never blocked.
Rejected: holding input only for presentations that grow from a trigger.
DEC-19 — A phone menu stays beside its trigger¶
Reference: spec:AST-094/DEC-19
Decider: cixzhang, 2026-10-26
On a compact touch screen an anchored menu keeps the layer runtime's normal placement beside its trigger, inside the viewport gutter, so the trigger stays visible while the menu is open wherever the menu fits beside it; a menu taller than the room on either side follows the layer runtime's own fallback.
Rejected: covering the trigger, centered on it and aligned with its top or bottom, as UIKit's menu does.
DEC-22 — An edge band claims only on an element within the band¶
Reference: spec:AST-094/DEC-22
Decider: cixzhang, 2026-10-26
touch-action is set per element, not per touch, so the band's pan-x claim
and 15 px start can only hold on an element that lies within the band. On a
wider element an in-band touch decides at 10 px like every other claim, since
claiming pan-x across it would take the author's scrolling (DEC-13).
Rejected: a whole-element claim on a wider element.
DEC-18 — A scroll-edge pan may hold the page's rubber band from the first move¶
Reference: spec:AST-094/DEC-18
Decider: cixzhang, 2026-10-26
When every scroller under the finger is at its edge and the drag moves toward that edge, the browser would otherwise rubber-band the page before the pan reaches its 10 pt start (a reading of Mobile Safari's overscroll, not a measurement), so a sheet's pull would visibly fight the page. Cancelling only those moves, from the first, matches UIKit's sheet pull, and a real scroll is never cancelled. The trade-off: a list inside a sheet cannot pull to refresh from its top.
Rejected: cancelling moves only after the pan begins.
DEC-30 — A scroll-edge pan waits out a tap's wobble¶
Reference: spec:AST-094/DEC-30
Decider: Specs consistency ruling, 2026-11-09, applying DEC-18
The shared scroll-edge pan holds a finger only once travel along its axis reaches a tap's 5 px wobble, so a tap's click survives in every component that uses it. The trade: a wobble toward the edge from 5 px until the pan begins at 10 pt loses its click. The 5 px point is DEC-29's Mobile Safari reading.
The 5 CSS px tap allowance lives in gestures/tapWobble.ts (TAP_WOBBLE),
shared by the pan recognizer and BottomSheet's drag; measured in Mobile Safari,
so it stays out of the UIKit tables.
DEC-25 — A pager pages as UIKit measures it¶
Reference: spec:AST-094/DEC-25
Decider: cixzhang, 2026-11-01
A pager, a Carousel given hasSnap={useSnapPaging()} where the pager runs, and Lightbox's gallery pick the rest page and
start the settle as UIKit's paging scroll view does on iOS 26.2. UIKit
chooses the page by a speed threshold, the same 300 pt/s at 10, 25 and 40 %
of a page, not by a projection, and starts a slow release's settle from rest.
The owner tried this paging on the pager and the paging Carousel on
2026-11-01, with a trackpad and on a phone: "trackpad is good", "phone good".
This narrows FR3 and FR6 for paging only; every other release keeps them. A
page change during a drag starts from rest. A paging release decides by FR3's
paging rule, and its settle starts as FR6's paging paragraph says; FR37
applies unchanged.
Rejected: projecting a paging release with a deceleration rate; handing a slow paging release's velocity to the settle.
DEC-26 — A gesture component's motion springs from measured roles; a tap component's tap-started motion plays the theme's tokens¶
Reference: spec:AST-094/DEC-26
Decider: cixzhang, 2026-11-02
Motion that a gesture drives continues the person's hand. A release that
carries the gesture's velocity starts at that speed and settles on a spring
under every pointer: a flick with a mouse throws as a flick with a finger does.
In a component whose main interaction is a tap, motion that a tap, a click, a
hold, a key or the program starts has no speed to carry, so it plays the
theme's motion tokens, its duration and easing scaled by tempo, under every
pointer, and a theme's timing reaches it as it reaches every other timed
motion. A part that follows a pointer is not timed motion, so it follows every
pointer. The theme's tempo scales a gesture's spring and its character
offsets the role's measured bounce by the role's fixed weight, so one theme
feels the same for both kinds of motion.
The owner decided this on 2026-11-02. Motion stays with the theme's duration, but an element that follows an interaction is outside those timings. A mouse release settles on a spring from the release speed, so a flick keeps its throw. The theme's character shapes those springs and its tempo scales them. Any interaction that involves a gesture uses a spring. A tap has no velocity, so an interaction without a gesture uses the default motion, which applies the theme's motion tokens.
This narrows the measured motion roles of DEC-1, DEC-3 and DEC-15 to motion a
gesture drives, and extends the Non-goals' theme timing to every pointer.
Measured input timings, such as who gets a touch, hold durations and flick
speeds, stay internal values and are not motion roles. A tap component's touch
exit that no gesture drives plays the theme's exit duration and easing, and a
gesture component's plays its spring; the theme's exit switches still never
remove it (spec:AST-090 DEC-5).
Rejected: keeping the measured springs for motion a tap starts under a finger.
Rejected: a theme curve for a mouse release, which stops a flick dead.
Rejected: following a pointer only under a finger.
On 2026-11-04 the owner set the unit of that choice: a component's main interaction. A component whose main interaction is a gesture plays springs for all its motion, a tap inside it included, and a component whose main interaction is a tap plays curve tokens, so each component's pieces stay coordinated (FR45).
DEC-27 — Android claims rest on emulator evidence¶
Reference: spec:AST-094/DEC-27
Decider: cixzhang, 2026-11-03
No Android phone is at hand to check Android claims, so Chrome with Gboard in the Android emulator proves them, at the exact head under review, with animations at normal scale and with animations removed, plus a slow-device profile. No human check on a device is needed for an Android claim. iOS Safari claims keep real-device evidence. The owner decided this on 2026-11-03: emulator evidence for anything Android-specific, with no human checks there.
Rejected: a physical Android phone as a gate or as a follow-up check.
DEC-31 — Device and emulator evidence carries across a main merge that touches none of the pull request's hand-edited source files, direct imports or shared motion and layer modules¶
Reference: spec:AST-094/DEC-31
Decider: cixzhang, 2026-11-09
Evidence taken on a device or in the emulator at an earlier head still counts
at a later head that only merges main, when the pull request's own changes
are byte-identical between the two heads and the merge changed none of the
files the pull request changes, none of the files those changes import
directly, and none of the shared motion and layer modules that the verification
row lists. Otherwise the evidence is taken again at the new head. This is an
exception to DEC-27's exact-head rule for heads that only merge main; DEC-27
holds for every other head.
Rejected: a new take after every main merge.
Amended by the owner (cixzhang, 2026-11-10): once the owner has passed a
behavior on a device, a later head of the same pull request is verified by a
side-by-side on the same devices against the head she passed, with the same
steps and frame-checked evidence, instead of by her; it returns to her only when
the side-by-side shows a major difference. A first check of a behavior still
goes to her. The owner's words: "Can you just check it yourself after and only
ahow me if theres major differences".
Amended by the owner (cixzhang, 2026-11-13): a merge whose only overlap
with the pull request's own files is generated files (route manifests, registry
lockfiles, CLI fixtures) keeps the evidence when CI proves each of those files
regenerates identically at the new head. A merge that changes one of the pull
request's hand-edited source files, a file its changes import directly, or a
shared motion or layer module still requires a new take. The owner's words:
"Yes, when CI proves they regenerate identically."
Amended by the owner (cixzhang, 2026-11-12): evidence also carries over a
commit, or a merge's change to the pull request's own files, that touches only
test-only files or knowledge records. A test-only file is one under a
__tests__/ folder or named *.test.* or *.spec.* that no rendered or
shipped code imports, a story included; a knowledge record is Markdown under
docs/specs/, docs/architecture/, docs/families/ or docs/design/. A
release note under .changeset/ carries the same way, since it renders
nothing (spec:AST-030 FR13). Any other file, apart from the generated files above, requires a new take. The
owner's choice: "Test and spec-only".
DEC-28 — Sheet stretch at the tallest detent¶
Reference: spec:AST-094/DEC-28
Decider: the owner, 2026-11-03
Decided by the owner in a feel check on a phone: at a sheet's tallest detent, a pull that carries its content past its end continues as the sheet's stretch, and a reversal hands it back (FR14's one exception).
Rejected: keeping the whole gesture with the content (the strict nested-scroll rule).
DEC-29 — A sheet's pull waits out a tap's wobble¶
Reference: spec:AST-094/DEC-29
Decider: Specs consistency ruling, 2026-11-09, applying DEC-18
Mobile Safari commits a kept first move of 5 px to the native pan (iOS 26.2 Simulator; a kept move of 4 px commits nothing; the author's earlier Mobile Safari 27.0 run committed at 7 px), so BottomSheet cancels from a first move that reaches a tap's 5 px wobble. Once the native pan is committed, no later cancel stops it, and the sheet's content rubber-bands under the finger while the sheet moves beside it. WebKit ends a touch's click when one of its moves is cancelled, so waiting out the wobble keeps a tap's click on a control in the sheet. The trade-off: a tap that wobbles 5 to 8 px toward the edge loses its click.
DEC-32 — A held swipe row stays under the finger¶
Reference: spec:AST-094/DEC-32
Decider: cixzhang, 2026-11-11
While a finger holds a swipe row, from the moment the swipe claims the gesture
the row's offset equals the finger's travel since touch-down, every frame,
until release; past the confirm point a lead grows to the confirmation offset
on the measured confirm motion (spec:AST-057 FR5) and the row keeps that
lead. No spring follows the finger; the release's settle keeps its measured
roles. The owners' words: "…If im dragging a portion of the listitem undermy
finger i expect that to stay under my finger the entire duration of the
gesture until i release".
Open questions¶
- OQ1 — Scroll view bounce-back curve. What curve brings a scroll view
back from an overscroll? It is not a single spring from rest; the rubber
band itself is settled. (
checkable) - OQ2 — Rotation threshold. What rotation starts a rotation gesture? No
stored threshold is readable, and the simulator cannot script two-finger
rotation. (
checkable) - OQ5 — The menu's drift allowance. The 13 pt drift allowance (FR29)
sits between a 12 pt move that opened the menu and a 14 pt move that did
not. Is that bracket its justification, or does it need a finer
measurement? (
owner decision) - OQ6 — Opening a sub-menu without a lift. Resolved by
module:DropdownMenu/useMenuPressDEC-8: a finger resting on a sub-menu row never opens it; a lift on the row does (its FR10). - OQ7 — The opening haptic. UIKit plays a haptic as a held finger
opens a menu; a page in iOS Safari cannot (FR23). Where does the menu record
that gap? (
owner decision) - OQ8 — Withdrawing a tentative open. Resolved by
module:DropdownMenu/useMenuPressDEC-8: nothing withdraws an open, so a screen reader hears one open and one close (its AR5). - OQ10 — A sub-menu with its parent visible. Should a drilled-in sub-menu
open in place, the menu's box growing to it with the parent menu visible
behind it, as UIKit's menu does? This is look and feel; today the sub-menu's
rows replace the parent's (FR34). (
owner decision)
本页原文 Markdown:在 AtomGit 查看·内容源自开源项目 as/astryx