Record multi-pane ring and unfold validation
This commit is contained in:
@@ -0,0 +1,30 @@
|
||||
# Mobile added-pane ring and unfold layout
|
||||
|
||||
The preview is the next workspace pane in a stable circular tree order, rather
|
||||
than the previously active pane. Repeated quick-switch taps reach every added
|
||||
pane before wrapping. Chats present only in the session list are excluded.
|
||||
The next preview enters below the incoming active chat; the former active exits
|
||||
as a bounded snapshot, so three-plus panes keep the same glued tape geometry.
|
||||
|
||||
The560ms motion uses quintic easing with zero endpoint velocity and acceleration.
|
||||
Existing speed and reduced-motion settings apply. New panes added on a narrow
|
||||
mobile layout save horizontal splits; the sidebar preference is compact, leaving
|
||||
room on unfold. When all panes fit they appear side by side; otherwise the tape
|
||||
remains available rather than leaving only one un-switchable pane. Existing
|
||||
explicit split layouts are preserved.
|
||||
|
||||
Checks:965 chat tests pass (peak1836MB,74s; /tmp/memwatch/out.D3IUjU).
|
||||
Final workspace29 pass including direct retained-pane jump, four-pane repeat
|
||||
loop, draft identity retention, joined edges, removal, resize and restore
|
||||
(/tmp/memwatch/out.cmZfim). Phone-to880px integration preserves draft/state and
|
||||
asserts horizontal split plus side-by-side rectangles. Analyze clean
|
||||
(/.../flutter-analyze.edCYlB). Fixture build succeeded.
|
||||
|
||||
Inspected browser evidence:
|
||||
- /tmp/review/mobile-pane-ring/02-film-label-Expand-Release-notes-sheet.png
|
||||
- /tmp/review/mobile-pane-ring/07-unfolded.png
|
||||
- /tmp/review/mobile-pane-unfold/02-unfolded-two.png
|
||||
The fixture has8 chats; only4 were added. Taps cycled Release notes→api refactor→
|
||||
Billing bug→Docs pass→Release notes, then widened to horizontal panes. Browser
|
||||
errors empty; owned capture browsers/loopback servers cleaned. No native Fold
|
||||
was used for testing and no operator chat was modified.
|
||||
Reference in New Issue
Block a user