feat(Toast): every pointer swipes a toast, on the shared gesture host (spec:AST-094 FR43) by vjeux · Pull Request #8678 · meta/astryx

vjeux · 2026-10-27T12:01:51Z

Depends on #8144 and #8676 (and their predecessors). Review only this PR's change: vjeux/astryx@d54551c...9118ec7 and the commits vjeux@363d754, vjeux@786d25e, vjeux@c027f5f, vjeux@81bd53b and vjeux@55fe123 (the rest merge #8676 and #8144)

Primary intent

Toast's swipe takes every pointer and wheel scrolling, and its own swipe (a fine pointer, or presentation="toast") runs on the shared gesture host (spec:AST-094 FR43). Other templates don't fit: it changes behavior.

User or maintainer impact

A mouse now swipes a toast in both presentations; once the swipe takes the drag, its text selection is cleared and none follows (FR41).
A mouse wheel or trackpad scroll toward the edge swipes it too once nothing under the pointer, the page included, can scroll that way (FR43).
Under Reduce Motion, a mouse's, trackpad's or pen's banner release cross-fades only on a coarse primary pointer, and otherwise changes at once (FR43, design:reduced-motion DR3).
The own swipe begins after 10 pt, not 8 px (FR17).
A second finger no longer cancels a started swipe; one landing earlier leaves the page its pinch (FR10).
Unchanged: the follow, fade, release rule and exit.

Problem and solution fit

Toast kept private touch and pen listeners with their own slop, second-finger rule and velocity tracking. It now attaches a one-way PanGestureRecognizer and reads its travel and release velocity. Both pans let the host manage the card's touch-action (FR24).

Authority

spec:AST-094 FR43, FR41, FR10, FR17, FR24.
Components use the shared gesture APIs (feat(core): Switch follows a finger the way the iOS switch does #8124).

Change and evidence

useToastGesture.ts: the pan replaces the listeners. Both pans decline a scroll the page can take; the banner marks only a finger's release as touch. Docs, and a presentation="notification" story.
Toast.spec.md: FR4 states the mouse, wheel, trackpad and second finger.
jsdom, red first: no own touch listener; a second finger keeps a started swipe; a mouse drag, a notch and a trackpad scroll swipe both presentations; a scrollable page keeps the scroll.
Real input, Chromium and WebKit, red first: a mouse drag across the text dismisses and selects nothing; a notch and a trackpad scroll dismiss; a scrollable page scrolls until its edge; under Reduce Motion a mouse release of the banner changes at once. With presentation="toast", a finger's drag toward the edge dismisses; away leaves it.

Scope

This PR has one primary intent.
Independently removable deltas were removed or split.
Public text and artifacts contain no internal Meta context.

Size: +1,313 / −563 (tests 949). Toast's import (the CI's measurement): JS 95,551 → 94,818 B gzip; no CSS change.

Testing

pnpm exec vitest run packages/core/src/ (16 workers): 15,261 pass (563 files), with no unhandled error; the node project (16 workers): 14,436 pass; its reds are two story-tree.test.ts cases (see test(storybook): run the story-tree check where Storybook is built, and bring the tree back to its shape #8509), two cache.test.mjs cases (see fix(cli): a crashed run's release install is recognized by the Node it ran on, whatever its name #8520) and the touch-module bundle test below. The red-first tests fail on the previous head.
pnpm test:interaction ToastSwipe: Chromium 31/31; WebKit (the harness container script) 26 passed, 5 skips (3 Chromium-only; the 2 pen tests, which drive Chromium input). Real touch with a coarse pointer, and a real mouse and trackpad scroll (the web input drivers) with a fine one, no engine emulation.
Root pnpm build, the Storybook build, pnpm typecheck, CI=true pnpm lint (0 errors; the one warning in Toast's files is main's) and pnpm check:knowledge: clean. A merge-tree with main (90da4a7) is clean (rc 0). The touch-module bundle test's "is absent from the root entry" red (scripts/touch-support-bundle.test.mjs, from main's refactor(core): one shared touch module that components import directly, reached by Lab through internal/touch #8465) is the one test(core): a touch component's import carries its gesture code, and nothing else does #8671 resolves.

Writing rubric results

R1 narration: FR4's wheel, trackpad, and second-finger sentences, the compatibility line, and the two edited current-state bullets state what the system does, in the present tense; none found.
R2 research: none in the record.
R3 evidence: the FR4–FR5 verification row names its inputs and test files, not changes; no basis cell changed.
R4 rejected alternatives: none.
R5 change references: none.
R6 open questions: none; the record keeps "None".

… is down off the sheet (spec:AST-094 FR10) The lone-finger hold counts only the fingers the pan tracks, so a second finger on plain page content left the sheet's finger held, and the moves of a pinch across the sheet's edge were cancelled. This test fails until the host counts every finger on the screen.

…is down anywhere (spec:AST-094 FR10) The lone-finger hold counted only the fingers the pan tracks, so a second finger on plain page content left the sheet's finger held, and a pinch across the sheet's edge had its moves cancelled. The host now applies a recognizer's hold only while the move's event reports one finger on the screen; the pan's own count still covers two fingers on the sheet.

An attach reads the element's own will-change in a task of its own. A shared animator (animatorFor) is never detached, so its node can leave the document with that read still waiting, and the read then forces a style pass on a node with no style: a test run that mounts and unmounts many pagers piled up such reads until a later wait timed out. The read now skips a node out of the document; a promotion that needs it reads it then, as one on a node attached in the same task does. A detach and dispose already cancel it. The new test fails on the previous code (one read of a removed node); the in-task read test now puts its element in the document, where the read happens.

…ter the browser takes the touch A host that stopped feeding the finger at the takeover and still delivered the lift would have passed. Each transition now records the list's scrollTop, and the test expects a 'changed' while the list is scrolled (spec:AST-094 FR20: it follows the scroll to the lift).

…keover) into the host line

…her browser test) into the arena fixes The host-owner changeset keeps this PR's own listeners for the scroll lock and finger-scroll watch, with meta#8336's lone-finger scroll-edge hold.

…of the document) into meta#8270

…sture system (spec:AST-094 FR24, FR43) utils/pressFeedback.ts reaches gestures/coarsePointer.ts, so a page whose only touch work is press feedback carries a gesture module, and a bundle check that counts gestures/ code finds it in the root and hooks entries. The coarse-pointer query belongs with the environment queries. This test walks the controller's import graph and fails until it reaches no module under gestures/.

…ries in utils/ (spec:AST-094 FR43) gestures/coarsePointer.ts becomes utils/coarsePointer.ts, beside utils/touchQueries.ts, with its test; the gesture host's selection lock, the press controller and the pointer test helper import it from there. The press controller's import graph now reaches no module under gestures/, so a page whose only touch work is press feedback carries none of the gesture system. No behavior changes.

…/) into meta#8309

…/) into meta#8315

CI's lint rejected the three Array<T> types the previous commit added (@typescript-eslint/array-type); the test now names its record once (WatchTransition) and reuses it.

…e arena's reset The arena resets a recognizer to possible after it ends, as UIKit does, and the transition listener records that too, so the last transition is possible: the test now asserts the ended-then-possible tail.

…/) into meta#8336

…/) into meta#8320

…finger, meta#8589's watcher test, its lint fix; meta#8076 3bfd7c3; the coarse-pointer query in utils/) into meta#8293

…nter query in utils/) into meta#8358

…nter query in utils/) into meta#8356 # Conflicts: # packages/core/src/gestures/GestureHost.ts # packages/core/src/gestures/fingerScroll.ts # packages/core/src/gestures/pageHold.ts # packages/core/src/gestures/selectionLock.ts # packages/core/src/utils/pressFeedback.ts

…nter query in utils/) into meta#8360

… FR19, FR24) Under a fine primary pointer: each element that uses a gesture keeps one passive pointerdown listener and the page none while idle; a mouse or a pen pans, its page listeners lasting only the press; a press consumer takes a mouse press with no feedback-only mode (DEC-21); a pan writes its touch-action for a touchscreen laptop's finger (FR18); perEventPointer is taken as any attach, with no warning; a secondary button starts nothing. All but the last fail until the host attaches for every pointer.

…e coarsePointer move) into uikit/c25-toast-swipe

…nues the release spec:AST-094 FR37: a release whose velocity points back toward rest springs the card back, however far out it is. FR38: after a dismissing release the retract starts at the card's release velocity; a release faster than the curve can start carries the card out sooner. architecture:component-style-authoring INV6: the touch module imports the settle row alone. design:reduced-motion DR2: under reduced motion on a touch screen, a toast-presentation card fades out before its row closes. architecture:react-component-runtime INV3: the mount-flag Effect is gone; the two-frame check reads whether the card is still in the document. The follow test reads long tasks only in Chromium: the harness's long-task log refuses to answer in WebKit, which has no Long Tasks API.

# Conflicts: # packages/core/src/Toast/__tests__/ToastSwipe.interaction.browser.spec.ts # packages/core/src/Toast/toastSwipe.test.ts # packages/core/src/Toast/toastSwipe.ts

… the scroll brake for a finger only (spec:AST-094 FR11, DEC-21) A mouse or a pen press paints at once, inside a scroller too; a mouse press on a scroller a flick set moving still presses, as the brake is a finger's. The brake case fails until the tracker brakes only a touch.

… (spec:AST-094 FR43) A drag from the edge band begins a screen-edge pan for a finger only, unless the caller allows another pointer. The mouse and pen case fails until the recognizer defaults to touches.

… lift and the browser's menu, keeps a kept press's finger, and goes when the page hides From the review of this pull request, three cases fail on its head: - an armed press installed the page listeners without the claiming ones, so a claimed finger's touchend stayed passive and the browser's menu opened during a claimed long press (spec:AST-094 FR21); - a kept press got its blocking touchmove during an armed press, but its moves were cancelled only where the primary pointer is coarse, so a held stepper on a touchscreen laptop lost its finger (FR11, DEC-21); - a page hidden mid-press cancelled the press but kept the page's listeners until the next lift anywhere (FR24).

…lift and the browser's menu, keeps a kept press's finger, and goes when the page hides - A finger's or a pen's armed press now brings the claiming listeners (the cancelable touchend and the contextmenu canceller) with the page listeners, as wherever the host installs, so a claimed lift clicks nothing and a claimed hold opens no browser menu (spec:AST-094 FR21). A mouse's press needs neither and adds neither. - A kept press keeps its finger under any pointer: its target blocks and its moves are cancelled once its press is delivered, not only where the primary pointer is coarse (FR11, DEC-21). - A page hidden mid-press releases the armed press as a blur does, so the page's listeners go with the cancelled press (FR24).

…ies meta#8320, meta#8076 and main) into uikit/c25-toast-swipe

…'s selection An action group's press is a long press with no minimum duration, so it claims at the press's pointerdown, before any movement. The drag selection hold then cleared the page's selection, so a plain click on a group's button left its Copy or Cut with nothing to act on. The case fails on this head: the selection is gone after the pointerdown.

…uikit/c25-toast-every-pointer

…age's selection The drag selection hold cleared the page's selection when any mouse or pen contact was claimed, but an action group's press claims at its pointerdown, before it has moved or selected anything, so a plain click on a group's button left its Copy or Cut with nothing to act on. A claim before any movement now keeps the page's selection: the hold still refuses a new one, and puts the page's back over a selection that appears while it runs. A claim after movement clears what its drag selected, as before (spec:AST-094 FR41). The case before the new one now waits for its hold to end a task after the lift, so no hold outlives that test.

…t every pointer does - GestureHost's header, the gestures README and coarsePointer.ts no longer describe the coarse-only host: a finger or a pen takes the touch-down lock under any primary pointer, a kept press's finger is kept during a fine pointer's press too, and recognizers attach for every pointer while the page listeners last a press (spec:AST-094 FR19, FR24, FR41, FR43). - The fine-pointer selection case asserted the replaced rule and passed only because it read iOS WebKit's inline lock without iOS WebKit: it now asserts the lock a fine pointer's finger and pen take, and that a mouse takes none. - FR41's sentence and its verification row say that a press claimed at its own pointerdown, before it moves, keeps the page's selection, while a drag that moved before its claim loses what it selected.

…ion, in the present tense The sentence said a drag that moved before its claim loses the selection it started, but the hold clears the page's selection then, whatever made it; and an unclaimed mouse drag kept "today's" behavior, a phrase that ages. It now says a claim after movement clears the page's selection, a press claimed at its own pointerdown keeps it, and an unclaimed mouse drag keeps its released behavior.

meta#8665's review fixes: an armed press under a fine pointer brings the claiming listeners, keeps a kept press's finger and goes when the page hides; a press claimed at its own pointerdown keeps the page's selection; FR41 says what a claimed drag does with the selection; meta#8360's input-stream notes. The merge is clean.

…uikit/c25-toast-every-pointer

Toast.spec.md records what this branch ships: the `presentation` concept (`adaptive` by default, `toast`, `notification`), the notification swipe in FR4 and its retract in FR5, the released default it changes under a finger, and the current-state bullets and gap text the notification presentation closes (a release moving back springs back, the settle starts at the release velocity, and reduced motion fades on a touch screen). The toast presentation keeps its listed gaps: net travel, a theme-timed settle, a second touch that cancels, and no projection.

Toast.spec.md records what this branch adds: a mouse drag, a wheel and a trackpad scroll swipe a toast in both presentations (FR4, with the page keeping a scroll it can still take and a claimed drag holding off text selection), a second touch never ends a swipe that began, and only a finger's release is a touch release under reduced motion. The current-state bullet on the mouse goes; the toast presentation keeps its listed gaps (net travel, a theme-timed settle, no projection, and a reduced-motion fade that follows the primary pointer).

astracat-bot

Approval of this pull request waits on an engineering owner's decision. This head writes new rules that main does not state into spec:AST-094 FR41 (a mouse or pen drag a gesture claims clears the page's text selection) and into Toast's record (the presentation concept and the FR4 and FR5 rewrites). An engineering owner records that decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner. Separately, please rebase as #8076, #8121, #8144, #8360, #8665, #8666 and #8676 land, or retarget onto the immediate predecessor's branch, so that the diff shows only this pull request's nine Toast files instead of 37,002 changed lines.

[Automated review]

astracat-bot · 2026-10-29T22:51:05Z

  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-017` FR59; DEC-9).
+  (`spec:AST-017` FR59; DEC-9). A mouse or pen drag that a recognizer claims


This adds normative text that FR41 on main does not state: there a mouse "otherwise keeps its released behavior", and the verification row fails any change to mouse selection. It needs an engineering owner's approval for this head (/approve-spec <full head SHA>), or it can stay in #8665, where it originates.

astracat-bot · 2026-10-29T22:51:05Z


- Released default preserved: `yes`
- Compatibility class: records shipped behavior; no public change
+- Released default preserved: `no`: under a finger the default `adaptive`


This changes Toast's current record. The presentation concept, the FR4 and FR5 rewrites, and this released-default change need an engineering owner's approval for this head before they govern.

…r, and every pointer swipes Toast takes `presentation` ('adaptive' by default, 'toast', 'notification'). Under a finger the swipe and the exit follow the iOS notification banner (values and sources in motion/uikit/toast.ts): the card follows past a first distance at a ratio, a release decides on the card's offset or the finger's speed at the lift, a release moving back springs back, a drag that turns back stretches the card and springs it back, and every dismissal retracts the card past its edge. Toast's own swipe (a fine pointer, or `presentation="toast"`) runs on the shared pan for every pointer, a finger, a pen and a mouse, with a flick at any travel read from the shared release filter at the lift. Toast.spec.md records the Presentation concept, FR4, FR5 and the gaps that remain. One solution from four pull requests: meta#8121 (the banner swipe and `presentation`), meta#8144 (the turn-back stretch), meta#8678 (every pointer on the shared pan) and meta#8047 (a flick at any height). Left out, since no spec decides them yet: the wheel and trackpad swipe, and the text-selection hold during a mouse or pen drag.

astracat-bot

Approval waits on an engineering owner's decision, and changes are needed whatever that decision is.

This head writes new rules into Toast's record that main does not state: the presentation concept with its public prop and type, the notification-banner FR4 and FR5 text, a trackpad scroll that swipes a toast, and a released default that is no longer preserved. An engineering owner records the decision by commenting /approve-spec <full head SHA> on this pull request, and the author may do so as an engineering owner. Otherwise the text is dropped.

Blocking findings:

Desktop behavior change needs an owner decision: Toast's swipe now takes a mouse drag, a wheel notch and a trackpad scroll for every desktop user (useToastGesture.ts:107-117, useToastBannerSwipe.ts:193-200). Gate it to touch input, or cite the decision that covers it.
A mouse wheel notch dismisses a toast, but spec:AST-094 FR43 and DEC-24 on main keep a mouse wheel's notches off every pan. Take only a trackpad's scroll, if any, and flip the tests at ToastViewport.test.tsx:1339 and :4204.
A mouse drag that starts on a toast's text swipes the toast away and clears the page's selection, but FR41 on main leaves such a drag to the text and never clears an existing selection. Drop this head's FR41 rewrite and fix the test at ToastSwipe.interaction.browser.spec.ts:908.
The diff carries 37,002 authored lines and conflicts with main. Most of it is older copies of #8076, #8360, #8665, #8666 and #8676, now on main in other forms, and of the open #8121 and #8144. Rebase so the diff shows only this branch's Toast change.

[Automated review]

astracat-bot · 2026-11-03T23:38:52Z

+  });
+  const sessionRef = useRef<SwipeSession | null>(null);
+
+  const pan = useGestureRecognizer(


This pan has no pointer-type gate, so every desktop user with default props now swipes toasts with a mouse drag, a wheel notch and a trackpad scroll. That is a desktop behavior change, and it needs an owner decision. Keep the base's touch-and-pen gate (allowedPointerTypes: ['touch', 'pen']), or cite the decision that covers it.

astracat-bot · 2026-11-03T23:38:52Z

+  const pan = useGestureRecognizer(
+    rootRef,
+    () =>
+      new PanGestureRecognizer({


allowedScrollTypes is unset, so this branch's pan takes its default ['continuous', 'discrete'], and one mouse wheel notch toward the edge dismisses the toast. spec:AST-094 FR43 on main has a pan take "never a mouse wheel's notches" (DEC-24). If a trackpad scroll stays, use allowedScrollTypes: ['continuous'], as an earlier commit here had. The same applies to the banner swipe's pan.

astracat-bot · 2026-11-03T23:38:52Z

+  (`spec:AST-017` FR59; DEC-9). A mouse or pen drag that a recognizer claims
+  takes no new text selection for that drag only. A claim made after the
+  drag has moved clears the page's selection; a press claimed at its own
+  pointerdown, before it moves, keeps it. An unclaimed mouse drag keeps its
+  released behavior.


FR41 on main now reads: a claimed mouse or pen drag "never clears an existing selection; a drag that starts on selectable text is not claimed." This text says the opposite, so it conflicts with the current record. Drop this edit and its verification-row change, and conform to main's FR41.

astracat-bot · 2026-11-03T23:38:52Z

+    await expect(page.locator('.astryx-toast')).toHaveCount(0);
+  });
+
+  test('a mouse drag across the toast’s text swipes it away and leaves no text selected (spec:AST-094 FR43, FR41)', async ({


Under FR41 on main, a drag that starts on the toast's text is not claimed, so it selects the text and leaves the toast. This test asserts the opposite: a swipe with nothing selected. Flip it once the head conforms.

astracat-bot · 2026-11-03T23:38:52Z


- Released default preserved: `yes`
- Compatibility class: records shipped behavior; no public change
+- Released default preserved: `no`: under a finger the default `adaptive`


This changes Toast's current record: "Released default preserved" becomes no, alongside the presentation concept and the FR4 and FR5 rewrites. An engineering owner needs to approve it at this head with /approve-spec <full head SHA>. The record also now lives at docs/specs/components/Toast/Toast.spec.md on main.

vjeux and others added 30 commits October 26, 2026 21:10

Merge meta#8356 (meta#8320 46fb7be) into meta#8358

45c93cc

Merge meta#8293 (meta#8320 46fb7be) into meta#8356

87144e2

Merge meta#8358 (meta#8320 46fb7be) into meta#8360

ab71d20

Merge meta#8589 (the watcher's browser test checks moves after the ta…

e79f0f5

…keover) into the host line

Merge meta#8336 (vjeux's two-finger scroll-edge fix; meta#8589's watc…

e744e52

…her browser test) into the arena fixes The host-owner changeset keeps this PR's own listeners for the scroll lock and finger-scroll watch, with meta#8336's lone-finger scroll-edge hold.

Merge facebook#8076 (3bfd7c3: the animator reads no style for a node …

2119cfa

…of the document) into meta#8270

Merge meta#8270 (meta#8076 3bfd7c3; the coarse-pointer query in utils…

e585b5b

…/) into meta#8309

Merge meta#8309 (meta#8076 3bfd7c3; the coarse-pointer query in utils…

c645a98

…/) into meta#8315

test(gestures): the watcher's browser test names its record type (lint)

fd4aa33

CI's lint rejected the three Array<T> types the previous commit added (@typescript-eslint/array-type); the test now names its record once (WatchTransition) and reuses it.

Merge meta#8589 (the watcher browser test's lint fix) into the host line

cdfff81

Merge meta#8336 (meta#8589's lint fix) into the arena fixes

f51a90c

Merge meta#8315 (meta#8076 3bfd7c3; the coarse-pointer query in utils…

2b148b1

…/) into meta#8336

Merge meta#8336 (meta#8076 3bfd7c3; the coarse-pointer query in utils…

0701cf6

…/) into meta#8320

Merge meta#8320 (cixzhang's ea8531c: the scroll-edge hold for a lone …

6c6da32

…finger, meta#8589's watcher test, its lint fix; meta#8076 3bfd7c3; the coarse-pointer query in utils/) into meta#8293

Merge meta#8356 (meta#8320 ea8531c; meta#8076 3bfd7c3; the coarse-poi…

f877b37

…nter query in utils/) into meta#8358

Merge meta#8358 (meta#8320 ea8531c; meta#8076 3bfd7c3; the coarse-poi…

2085cf6

…nter query in utils/) into meta#8360

Merge meta#8320 2fd9697 (F2's fY: meta#8076 3bfd7c3, the lint fix, th…

16dcb6d

…e coarsePointer move) into uikit/c25-toast-swipe

Merge meta#8121 a5e702673e into uikit/c25-toast-pull-away

13581ef

# Conflicts: # packages/core/src/Toast/__tests__/ToastSwipe.interaction.browser.spec.ts # packages/core/src/Toast/toastSwipe.test.ts # packages/core/src/Toast/toastSwipe.ts

test(gestures): the screen-edge pan stays off under a mouse and a pen…

e0adb9a

… (spec:AST-094 FR43) A drag from the edge band begins a screen-edge pan for a finger only, unless the caller allows another pointer. The mouse and pen case fails until the recognizer defaults to touches.

vjeux added 16 commits October 29, 2026 12:25

Merge meta#8360 045f666 (the re-folded gesture foundation, which carr…

cba466c

…ies meta#8320, meta#8076 and main) into uikit/c25-toast-swipe

Merge meta#8121 02a256a into uikit/c25-toast-pull-away

7506895

Merge meta#8676 fb86ce4 (the wheel input, on meta#8665 4362f35) into …

180fff5

…uikit/c25-toast-every-pointer

Merge meta#8144 ecf766d into uikit/c25-toast-every-pointer

ebaf4a8

Merge meta#8676 35445d0 (the wheel input, on meta#8665 c6c02fc) into …

147d1de

…uikit/c25-toast-every-pointer

Merge meta#8121 2b59f30 into uikit/c25-toast-pull-away

fc370d4

Merge meta#8144 260694b into uikit/c25-toast-every-pointer

c056718

vjeux mentioned this pull request Oct 29, 2026

feat(Toast): the swipe follows iOS notification banners under a finger #8121

Draft

3 tasks done

vercel Bot deployed to Preview October 29, 2026 22:27

View deployment

vjeux marked this pull request as draft October 29, 2026 22:38

astracat-bot Bot reviewed Oct 29, 2026

View reviewed changes

vjeux force-pushed the uikit/c25-toast-every-pointer branch from 55fe123 to 0e4fe36 Compare November 3, 2026 23:01

github-actions Bot added the needs:spec-owner-review Current knowledge records await owner approval label Nov 3, 2026

vercel Bot deployed to Preview November 3, 2026 23:15

View deployment

astracat-bot Bot reviewed Nov 3, 2026

View reviewed changes

vjeux mentioned this pull request Nov 4, 2026

chore(gestures): a pan's begin threshold can be read from each press #9953

Merged

3 tasks done

Navigation Menu

Repository navigation

feat(Toast): every pointer swipes a toast, on the shared gesture host (spec:AST-094 FR43) - #8678

feat(Toast): every pointer swipes a toast, on the shared gesture host (spec:AST-094 FR43)#8678
vjeux wants to merge 1788 commits into
meta:mainfrom
vjeux:uikit/c25-toast-every-pointer

vjeux commented Oct 27, 2026 •

edited

Loading

Uh oh!

astracat-bot Bot left a comment

Uh oh!

astracat-bot Bot Oct 29, 2026

Uh oh!

astracat-bot Bot Oct 29, 2026

Uh oh!

astracat-bot Bot left a comment

Uh oh!

astracat-bot Bot Nov 3, 2026

Uh oh!

astracat-bot Bot Nov 3, 2026

Uh oh!

astracat-bot Bot Nov 3, 2026

Uh oh!

astracat-bot Bot Nov 3, 2026

Uh oh!

astracat-bot Bot Nov 3, 2026

Uh oh!

This branch was successfully deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

vjeux commented Oct 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Primary intent

User or maintainer impact

Problem and solution fit

Authority

Change and evidence

Scope

Testing

Writing rubric results

Uh oh!

astracat-bot Bot left a comment

Choose a reason for hiding this comment

Uh oh!

astracat-bot Bot Oct 29, 2026

Choose a reason for hiding this comment

Uh oh!

astracat-bot Bot Oct 29, 2026

Choose a reason for hiding this comment

Uh oh!

astracat-bot Bot left a comment

Choose a reason for hiding this comment

Uh oh!

astracat-bot Bot Nov 3, 2026

Choose a reason for hiding this comment

Uh oh!

astracat-bot Bot Nov 3, 2026

Choose a reason for hiding this comment

Uh oh!

astracat-bot Bot Nov 3, 2026

Choose a reason for hiding this comment

Uh oh!

astracat-bot Bot Nov 3, 2026

Choose a reason for hiding this comment

Uh oh!

astracat-bot Bot Nov 3, 2026

Choose a reason for hiding this comment

Uh oh!

This branch was successfully deployed

Reviewers

Uh oh!

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

vjeux commented Oct 27, 2026 •

edited

Loading