2.3 KiB
Mobile tape switch and remembered peek height
Both chats move upward as one joined tape. The old active exits above the incoming live pane as a bounded snapshot; its single retained live tree loops in from below with a real small scroll viewport. This avoids duplicating live chat state. The default is 560 ms, globally scaled by the animation setting. Repeated activations queue the latest role until the current loop finishes. Reduced motion, first layout, or an unavailable fresh picture settle directly. The crossing-card rounded/shadow effect and its source file are removed.
Small layouts keep only the active chat's coloured bottom border. A 24 px touch and mouse target centred on that border adjusts the inactive height. The range is 48 logical pixels through the previous 20% maximum (the minimum yields to 20% on extremely short viewports). The saved fraction remains per-server in the existing workspace preference; old snapshots default to 20%, and keyboard or orientation changes constrain presentation without rewriting the preference.
The workspace exposes a deduplicated post-frame visible-session callback based on the actual mobile pair, collapsed active pane, or desktop split leaves. Retained offstage chats are excluded. Root integration wires this into sidebar visibility indicators.
Checks:
tool/memwatch/full.sh test/features/chat: 962 passed, zero failed/skipped, peak 1989 MB, 63 seconds./tmp/memwatch/out.Pi7Bqo.tool/analyze.sh: clean./tmp/flutter-analyzeoutput path is recorded in agent tool logs (final runflutter-analyze.zX3NNQ).- Fixture web build succeeded. Actual browser actions/captures inspected:
/tmp/review/mobile-tape-material/02-film-label-Expand-Fixture-chat-1-sheet.png,/tmp/review/mobile-tape-material/04-small.pngand return film. The 140px separator drag changed peek198.8 to58.8; reported viewport equals visible height58.8 and scroll pixels=max688.6. Chrome/private fixture server are cleaned by the capture kit on completion. - Tests cover joined tape edges and top exit/bottom wrap, queued reversal, retained drafts, min/max drag, snapshot cold restore/legacy validation, bottom-only phone borders, reduced motion and real small viewport scroll end.
These captures are browser evidence, not native Android device verification.