Repository navigation
fix(cmux-next): stabilize new-tab motion (current base) - #21620
teamleaderleo wants to merge 1 commit into
Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Bead |
|
Unclear: CI failed on
Not re-run automatically: Written by |
|
Agents: |
|
Holding this one: it doesn't fix the workspace-switch replay Leo sees in the nightly, and it reverts hardening from merged #21476 and #21501:
The one new idea, re-checking |
|
Closing: base already skips remeasuring when the row keys are unchanged and survives the Strict Mode effect replay. This diff would also undo two base fixes: #21476 (cancelling running animations) and #21501 (releasing finished ones), plus the motion-off check. #21781 is the current listMotion change. |
Focused new-tab motion fix on current feat-cmux-next base.
Validation: focused new-tab tests 10 passed, 31 assertions; diff-check clean.
Need help on this PR? Tag
@codesmith-botwith what you need.Summary by cubic
Stabilizes the new-tab list motion so it no longer remeasures row geometry or replays animations when the owner rerenders with the same row keys. The motion hook now keys off a string signature, a stable list root, and the row selector, and it re-observes a replaced root.
data-agent-motion="off"check; reduced-motion behavior now depends only on CSS variable overrides.Written for commit 5a07094. Summary will update on new commits.