fix(chat): use stock Navigator Back at every screen width

This commit is contained in:
2026-10-24 12:36:17 +01:00
parent 0ecd4a8487
commit f22afabd94
16 changed files with 262 additions and 53 deletions
@@ -0,0 +1,34 @@
# 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/`.
- No scroll-workaround, transition-duration change, backend mutation, service
restart or device testing. Full acceptance and deployment pending.