From an app built on core-v2:
Scrolling (#3, #4, #14)
- Each recognizer locks onto a touch within its first 6px: along its axis
and direction it holds the touch, otherwise it lets go. A new
onTouchmove binding cancels native scrolling only while a recognizer
holds the touch, so hosts use touch-action: manipulation and one
vertical gesture no longer disables vertical scrolling. Several
gestures on one host share touches through the same rule.
- .from.scrollEdge(scroller, edge) admits drag-to-dismiss only while a
scroller is at the edge (#5).
Feel
- recognition.distance sets what counts as full progress: pixels, a CSS
length, or a measuring function (#6).
- Choreographies receive overshoot, the drag past either end of the
clamped progress, and the settling spring starts from it (#7).
- Velocity is the least-squares trend of the last 100ms (#8).
- Defaults retuned to commitThreshold 0.25 and commitVelocity 0.2; the
slide presets use them (#9).
- Choreographies may set spring stiffness and damping (#10).
Hooks and helpers
- .onArm()/.onDisarm() run during a drag when releasing would start or
stop committing (#12).
- startedIn, nearEdge, atScrollEdge, anyOf, allOf start predicates (#15).
- Development builds warn when an operation's first frame moves a node
that was visibly at rest, the one-frame "pop" of mismatched open and
close choreographies (#16).
Docs: scrolling, ignored elements, animation performance, haptics, and
operating-system edge gestures including CloseWatcher/popstate for PWAs
(#11, #17, #18).
Verification: a Chromium harness with emulated touch (verify/browser)
checks swipes over scrollers, native scrolling beside gestures,
scroll-edge dismissal, onCommit inside pointerup, and the continuity
warning. Reverting the earlier capture fix makes it fail exactly as
reported ("none of the handles work").
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Faarh2Ts6StJPcz2mRiHiR
Rewrite the core-v2 internals without changing the public API or runtime
behavior. The four large files (types, scene, motion, gesture) become
layered modules with one responsibility each:
- shared/: geometry and environment helpers
- view/: originView recipes
- choreography/: effect types, presets, and composeEffects compositing
- actions/: forward/back/replace/above/under via one overload resolver
- scene/: SceneGraph storage, transitions (history rules), compositor
(styles and interactivity), spring (pure stepper + rAF driver), and
createOriginScene, which only wires them and owns async timing
- composables/: useOrigin and the node-scope injection key
- gesture/: builder, definition->policy normalization, start admission,
DirectionalTracker, and a GestureRecognizer session state machine
replacing fifteen loose closure variables
- components/: renderers and gesture hosts, plus their prop types
Verification (packages/core-v2/verify): differential fuzzing drives
main and this branch with identical random operation sequences and
pointer streams and requires identical scene state, styles, contexts,
callbacks, and promise results at every step. It caught every planted
mutation that applied. Benchmarks are at parity.
Also fix a pre-existing test that called the defineProps macro inside a
runtime defineComponent, and correct API.md's description of the flick
commit threshold to match the runtime.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Faarh2Ts6StJPcz2mRiHiR
Claude