fix(motion): unify live-indicator pulse amplitude across streaming dots - #211
Merged
Conversation
Kenji aesthetic-audit reminder 9 (msg `bacde601` 2026-06-24, finding #5): three streaming-state indicator dots have the same semantic ("live work happening") but their pulse amplitudes drifted: - `.maka-list-row-streaming-dot` keyframe at styles.css:2231 — `scale(1.1)` - `.maka-reasoning-panel-dot` keyframe at styles.css:11645 — `scale(1.15)` - `.maka-tool-output-stream-pulse` keyframe at styles.css:12634 — `scale(1.18)` The amplitudes pile up when more than one is visible at the same time (e.g. user in a turn that's streaming text AND a tool call is in flight) and the screen reads as agitated. Fix: settle all three to `scale(1.1)` — the calmest of the three because these dots run continuously while a turn is streaming and the larger pulses are visually loud at that frequency. List-row dot was already at 1.1 so this is a unification at the existing low end, not a raise. Single file, two keyframe value tweaks. Existing PR-202 styles.css edits are in different regions (onboarding rules + cubic-bezier sweep on transition values, not @Keyframes scale values), so no overlap.
jackwener
added a commit
that referenced
this pull request
Jun 24, 2026
…#213) Kenji aesthetic-audit reminder 9 (msg `bacde601` 2026-06-24, finding #1): composer micro-interaction scales drifted way past the global `button:active { scale(0.97) }` press range. Before: - `.maka-composer-tool-button:hover` — `scale(1.08)` - `.maka-composer-tool-button:active` — `scale(0.94)` - `.maka-composer-send-button:hover` — `scale(1.06)` - `.maka-composer-send-button:active` — `scale(0.96)` Tool buttons are quiet utility affordances (mic, attach) at the bottom of the composer; they don't deserve CTA-sized travel. 1.08 hover + 0.94 active reads as bouncy and tugs the eye away from the composer text input. The send button is a real CTA so it gets a hair more than the tool buttons but still inside the tactile range. After: - tool button: hover `scale(1.02)`, active `scale(0.97)` - send button: hover `scale(1.03)`, active `scale(0.97)` All within the global tactile press range. Single file, 4 value tweaks. No overlap with PR #211 (live-dot keyframes at lines 2231 / 11645 / 12634, far from this composer block at 6655-6706).
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
1 participant
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.
PR-FE-BUG-HUNT-6 picking up kenji's aesthetic-audit reminder 9 finding #5.
Bug
Three streaming-state indicator dots share the same semantic ("live work happening") but their pulse amplitudes drifted:
When more than one is visible at the same time (e.g. user in a turn that's streaming text AND a tool call is in flight) the amplitudes pile up and the screen reads as agitated.
Fix
Settle all three to `scale(1.1)` — the calmest of the three. These dots pulse continuously while a turn is streaming, and the larger amplitudes are visually loud at that cadence. The list-row dot was already at 1.1 so this is a unification at the existing low end, not a raise.
Diff
`1 file changed, 10 insertions(+), 2 deletions(-)` — two keyframes in styles.css. No overlap with PR #202's styles.css edits (those touch onboarding rules + the cubic-bezier sweep, not @Keyframes scale values).
Verification
Local disk still ~100%, couldn't run `pnpm install && pnpm test` end-to-end. CSS-only value change.