Uh oh!
There was an error while loading. Please reload this page.
fix(web): clean up composer resize animation - #5
Merged
Conversation
(cherry picked from commit c196f422ed387a1cc2cdb671b0472782e5610339)
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reworks the composer context strip's expand/collapse so widths are recomputed on every pass instead of latching remembered values that could go stale, and animates the controls through the Web Animations API at a fixed 180ms.
Cherry-picked from upstream
c196f422ed387a1cc2cdb671b0472782e5610339(pingdotgg/t3code#6209).Fits Pylon's motion rules: the animation is a discrete, bounded transition rather than a continuous repaint, and it early-returns on
prefers-reduced-motion: reduce.Conflict resolved Pylon-first
BranchToolbar.tsxconflicted structurally, because upstream and Pylon lay the strip out differently:min-w-0 flex-1 justify-end md:ml-auto md:flex-none).min-w-0 justify-start, adopted as E16 / #5555), because they describe the same thing — where the thread's work happens — while Usage sits opposite.Pylon's layout was kept and only upstream's animation machinery was taken: the
data-composer-context-controlmarkers, the strip'soverflow-x-clip overflow-y-visible, and the motion constants. Verified after resolution that upstream'sjustify-end md:ml-autodid not sneak back in and thatComposerUsageIndicator'sml-autoplacement survived. Added a comment at the divergence so the next merge does not silently undo it.Verification
BranchToolbartests pass (56)Model: Claude Opus 5 (1M context). Harness: Claude Code.
Need help on this PR? Tag
@codesmithwith what you need. Autofix is disabled.