Skip to content

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

TypeScript

spec(interaction-modality): Lab keeps no copy of the release-velocity filter (#8413)

Cindy Zhange36c64f1f026
diff --git a/docs/architecture/interaction-modality.md b/docs/architecture/interaction-modality.md
index cc2c641478..39be790cdb 100644
--- a/docs/architecture/interaction-modality.md
+++ b/docs/architecture/interaction-modality.md
@@ -7,7 +7,7 @@ authority: current
archive_reason: null
superseded_by: null
approved_by: cixzhang
-approved_at: 2026-10-24
+approved_at: 2026-10-25
owners: [cixzhang]
applies_to:
[
@@ -162,9 +162,9 @@ work.
previous one; a contact
still for longer than the stillness interval before lifting reads 0. It is not exported. No Core component keeps its own sample
buffer, velocity math, or alternative release filter; a component's flick
- threshold compares the tracker's release velocity. Lab cannot import the
- tracker; a Lab gesture keeps one local tracker with the same blend and
- stillness interval, so it reports the same velocity for the same motion.
+ threshold compares the tracker's release velocity. Lab keeps no copy of
+ it: no Lab component has its own sample buffer, velocity math, or release
+ filter, so Lab reports the same velocity as Core for the same motion.
## Allowed variation
@@ -243,17 +243,17 @@ reachability, newer-intent precedence, and the evidence/scope guard were approve
## Verification
-| Invariant | Evidence | Failure signal |
-| ---------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| INV1, INV2 | Programmatic-focus cases after keyboard and pointer input in representative component tests | Programmatic focus invents a modality, or pointer history paints the keyboard indicator |
-| INV3 | Direct-owner, wrapper-owner, replaceable-indicator, and nested-action cases | No indicator, two indicators, or replacement content can opt out |
-| INV4 | Keyboard, mouse, touch, and pen browser paths where applicable | Hover-only behavior, sticky touch hover, or unreachable action |
-| INV5 | Disabled, busy, and read-only DOM and activation assertions | Inactive control reacts, eligible control loses focus, or state changes with modality |
-| INV6 | Public API review and representative source inspection | A component adds caller-controlled modality without a separate API decision |
-| INV7 | Rendered-browser affected-state checks across geometry, clipping, scrolling, hit testing, built-in and custom-renderer paths | At an offered interaction point one modality loses every essential path, or evidence substitutes class equality for reachability/perceptibility |
-| INV8 | Owner-defined intent order, pending, close, cancellation, disablement, and unmount mutations | Older work changes current content, selection, status or announcement, visibility, focus, or activation after owner-defined supersession |
-| INV9 | Concrete-harm reproduction, representative normal/legacy/no-new-prop paths, and coincident public-delta inventory | Unsupported or aesthetic preference is treated as harm, unaffected behavior changes, or an API, layout, sizing, default, sticky, or exception delta escapes direct authority |
-| INV10 | Source boundary check over Core, a Lab-to-Core comparison on one recorded stream, and release-filter unit tests over recorded iOS pan and scroll-view streams | A Core component with its own sample buffer, velocity math, or release filter; a Lab tracker reporting a different velocity for the same stream; an export of the tracker; a non-zero release after a still pause |
+| Invariant | Evidence | Failure signal |
+| ---------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| INV1, INV2 | Programmatic-focus cases after keyboard and pointer input in representative component tests | Programmatic focus invents a modality, or pointer history paints the keyboard indicator |
+| INV3 | Direct-owner, wrapper-owner, replaceable-indicator, and nested-action cases | No indicator, two indicators, or replacement content can opt out |
+| INV4 | Keyboard, mouse, touch, and pen browser paths where applicable | Hover-only behavior, sticky touch hover, or unreachable action |
+| INV5 | Disabled, busy, and read-only DOM and activation assertions | Inactive control reacts, eligible control loses focus, or state changes with modality |
+| INV6 | Public API review and representative source inspection | A component adds caller-controlled modality without a separate API decision |
+| INV7 | Rendered-browser affected-state checks across geometry, clipping, scrolling, hit testing, built-in and custom-renderer paths | At an offered interaction point one modality loses every essential path, or evidence substitutes class equality for reachability/perceptibility |
+| INV8 | Owner-defined intent order, pending, close, cancellation, disablement, and unmount mutations | Older work changes current content, selection, status or announcement, visibility, focus, or activation after owner-defined supersession |
+| INV9 | Concrete-harm reproduction, representative normal/legacy/no-new-prop paths, and coincident public-delta inventory | Unsupported or aesthetic preference is treated as harm, unaffected behavior changes, or an API, layout, sizing, default, sticky, or exception delta escapes direct authority |
+| INV10 | Source boundary check over Core and Lab, a Lab-to-Core comparison on one recorded stream, and release-filter unit tests over recorded iOS pan and scroll-view streams | A Core component with its own sample buffer, velocity math, or release filter; a Lab component with its own sample buffer, velocity math, or release filter; a Lab component reporting a different velocity than Core for the same stream; an export of the tracker; a non-zero release after a still pause |
Real-browser evidence is required when the behavior depends on
`:focus-visible`, pointer capability, touch or pen synthesis, rendered focus
diff --git a/docs/specs/AST-100-release-velocity/spec.md b/docs/specs/AST-100-release-velocity/spec.md
index da0600a3a3..d412819b94 100644
--- a/docs/specs/AST-100-release-velocity/spec.md
+++ b/docs/specs/AST-100-release-velocity/spec.md
@@ -133,9 +133,8 @@ means for them.
Each component estimating velocity its own way reads the same flick at
different speeds in components of the same kind, and counts a finger that
-paused before lifting as a flick in one place and not another. One release filter, with one source in
-Core and the same filter in Lab, gives every component of a kind the same
-speed for the same motion. Reading a moving finger the way
+paused before lifting as a flick in one place and not another. One release filter, with one source in Core and no copy in Lab, gives every
+component of a kind the same speed for the same motion. Reading a moving finger the way
iOS does keeps flicks, paging, and dismissal near their thresholds where an
iPhone puts them, and the stillness reset stops a resting finger from flinging,
which is the one place the filter departs from iOS. What a speed means stays