2.2 KiB
Retained mobile chat entrance
A restored workspace reopens inside the retained Chat destination rather than
pushing a new route. Heroes cannot fly between two children of that same route.
It now enters with a short Material fade/up motion or the native
CupertinoPageTransition. The existing initial pushed chat page retains its
shared-avatar Hero. Its header Hero is scoped to that native-page path, avoiding
duplicate tags when the retained list and body coexist during fold/unfold.
ChatWorkspaceEntrance keeps its child mounted at full layout size, then changes
only paint translation/opacity. It never moves the GlobalKey workspace between
routes or replaces its panes. Hidden children disable tickers and interaction;
exit semantics are hidden immediately. Reduced motion is instant; the existing
global scheduler speed clock applies once to the 260ms base duration.
Checks:
- Six focused tests passed (
/tmp/memwatch/out.1OnK0u): real full-app restored multi-pane Back → Runs → Chat → Chat-retap, same workspace and active thread State instances, pane order/active id/peek ratio/drafts/scroll retained, and an intermediate entrance position. Both host entrance tests retain the same text field State/draft and check reduced motion. - 37 more passed (
/tmp/memwatch/out.GBlouj), including all 24 phone/wide list-detail consistency cases, initial shared-avatar Hero, saved workspace restoration and mobile quick switch. No duplicate Hero errors. - Analyzer clean (
flutter-analyze.8tHmKg). - Full-app fake-gateway browser film at 560x1000, seeded private saved layout,
80 rich messages and two panes: Back → list-row reopen, then Back → Chats-tab
retap both animate and retain the draft. Inspected before/after PNGs and both
contact sheets in
/tmp/retained-transition-final/; final focused textarea readback isRetained pane draft. Script:/tmp/retained-transition-capture.json.
The browser capture uses mouse clicks at phone layout width. Touch emulation in the generic capture kit could not re-enable semantics after a second page navigation; that failed setup is not device evidence. No Android hardware test or FPS claim. All owned capture/test/build processes completed. No deployment, server restart or live operator data mutation.