Files
pipelines/app/notes/chat-scroll-roundtrip-stock-back.md
T

72 lines
4.4 KiB
Markdown

# Stock chat Back after scrolling
User supplied exact reproduction: chat list → open chat → scroll to top → scroll
to bottom → Android Back. The previous rendering benchmark did not exercise this
sequence and did not establish the device-specific cause.
## Navigation correction
- Chat is now a real pushed Navigator page at **all widths**, including tablets
and unfolded devices. The old wide layout swapped a thread into the main page
and manually stepped the route back instead of popping a page.
- Detail page bars let Material/Cupertino supply Back automatically. No custom
Back callback, forced leading button, chat PopScope, timer or extra press.
- Chat no longer publishes an onBack override into shell chrome. Normal route
completion still clears selection and keeps the re-push safety guard.
- Home double-back remains home-only. New regression performs the user's scroll
sequence at 390/840 logical pixels, verifies a real route and a stock Back
action, pops with one system Back, and only then verifies two presses to exit.
- Existing navigation tests find native Back controls rather than an app-specific
key; deep-link tests await the actual reverse transition, not two zero-time frames.
## Evidence and limits
- 12 focused chat/deep-link/detail tests pass.
- Browser probe now supports OPEN_FROM_LIST, SCROLL_ROUNDTRIP, CHAT_VARIANCE and
PROBE_WIDTH. Screenshots prove top/bottom were reached; fixtures remain loopback.
- Quiet browser samples did not reproduce a multi-second delay: phone was about
481ms before; wide previously used an immediate manual route change. After the
real wide-page push, it pops in about 501ms with the native transition.
These numbers are NOT evidence that the reported physical-device delay is fixed.
- Captures: `build/scroll-back-repro-before/`, `build/scroll-back-wide-before/`,
`build/scroll-back-wide-after/`.
- Final exact-flow browser samples at phone Android-theme and wide Cupertino
sizes also pass: `build/scroll-back-final-phone/` and
`build/scroll-back-final-wide-cupertino/`. These remain browser, not device,
observations.
- Source landed as f22afabd. Full gate: clean analysis and **1,852 tests pass**.
- No scroll-workaround, transition-duration change, backend mutation, service
restart or device testing.
- `./install --web` succeeded; public URLs match installed JS SHA256
`cbd7e1629c6c2257afdf79156620e4c3d38997bb13851eee85a57d5af0c87d53`.
Web rollback: `app/build/web-before-stock-chat-back-1792841967/`.
- Combined APK publication verified below. Actual Android-device timing remains unverified.
- Stock-Back APK 29880696 completed and is preserved under
`build/candidates/stock-chat-back-29880696/`. Combined release **29880730**, also
including the requested rotating Stop icon, is now published/download-verified;
see `slow-stop-rotation.md`. Web is published too. Device timing still unverified.
## Follow-up: remove remaining router interception
- User reports the device problem persists and requests only removal of the Back
override. The router still treated a chat selection as an inline detail and
could dispatch `onPopToChat` from its root PopScope/fallback.
- Removed chat from that inline step-up path and disabled root double-back while
a chat session is selected. The pushed chat route retains stock Navigator Back;
no timing, scrolling, or animation workaround was added.
- Regression tests reject a blocking PopScope while chat is open, fail if the
legacy callback runs, and cover the exact scroll roundtrip at both widths.
- Checks: all 108 application tests pass; full gate clean analysis and 1,860 tests
pass. No physical-device testing; this does not prove the reported delay fixed.
- Updated APK **29880795** built and published at the user's request. Complete
authenticated APK downloads and feed metadata verified on HTTPS 8443 and 8096;
ZIP integrity, Pipelines display label, existing package ID and signing
certificate verified. SHA256:
`2ea329aacff8eee1bb228544abe4e0d109dbe72398c66aa211a61d18141f4cd0`.
- APK matches committed source cf784245, cache `82dc030735ab28c7610e`.
Concurrent uncommitted chat/shell changes appeared after build start; preserved
untouched and excluded from this release's source verification.
- Rollback feeds: `build/updates-before-router-back-removal-29880795/` and
`build/web/updates-before-router-back-removal-29880795/`. No service restart,
device installation or new web bundle deployment.