Repository navigation
🦔 fix: Keep System Messages Stable During Collapse - #16780
Merged
Merged
Conversation
Contributor
Author
|
Head: ce3dd9f. Keeps wake-up card width until the closing result body unmounts. Adds collapse and interrupted-reopen regressions for background-tool and subagent cards. Focused client tests: 41 passed. Client typecheck passed. |
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 free
to 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.
Summary
Collapsing a system background-task message briefly stretched its bubble to the full available width before returning to its compact header. Keep the expanded width while the result body animates closed, then restore the compact width when that body unmounts. Subagent wake-up cards use the same sizing rule.
How it works
Width and result-body lifetime now change together instead of releasing width at the start of the closing transition.
Type of change
Testing
tsc --noEmit: passed.npm run static-checks -- --against origin/dev: passed.ce3dd9f13a9e7a5b46b305ddfc8160342c2311fb: complete, no findings.Screenshots / recordings
Before/after recordings were captured from the running app at the same desktop viewport. Uploading with
gh --attachreturnedunsupported authentication type, so the recordings could not be attached.Risk / compatibility
No API, preference, theme, or animation-duration changes.
Checklist