fix(desktop): keep context gauge stable at the transcript tail - #4975
Open
me2seeks wants to merge 1 commit into
Open
fix(desktop): keep context gauge stable at the transcript tail#4975me2seeks wants to merge 1 commit into
me2seeks wants to merge 1 commit into
Conversation
me2seeks
force-pushed
the
fix/4973-context-gauge-tail-jump
branch
from
September 7, 2026 10:14
fdd155f to
6572edb
Compare
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
Keep the composer context gauge visually stable when the transcript reaches the live tail.
The tail transition fades the scroll-to-bottom control inside the same filtered dock surface as the composer. Chromium can re-raster that shared surface even though the gauge, model-control group, and composer DOM boxes never move; the thin gauge paths then visibly hop by a device pixel. This patch adds paint containment and a compositing hint to the scroll button’s existing 32px transition container, limiting the opacity repaint to that control.
The existing reader-scroll Storybook scenario now includes a real context gauge and asserts both sides of the contract: the scroll-button paint boundary is present, and the gauge SVG stays within 0.25px while returning to the tail.
Fixes #4973
Verification
npm --workspace @maka/desktop run typecheck:storiesnode --test packages/ui/dist/__tests__/composer-context-usage.test.js(2/2)npm --workspace @maka/desktop run build-storybooknode scripts/storybook-visual-smoke.mjs apps/desktop/storybook-static(312 stories, 339 theme renders)npm run check:renderer-architecture -- --base origin/main(101/101 fixtures; check passed)npm run astryx:surface-inventorynpm run lintnpm run format:checkgit diff --checkAI use
Tool and scope: Codex — diagnosis, implementation, browser verification, and test coverage.
Checklist
Does this PR entail a change in behavior?