Skip to content

Fix: Draw the top bar for a typing message only when what it shows changed - #188

Merged
b-re-w merged 1 commit into
developfrom
feat/key-draws
Nov 9, 2026
Merged

b-re-w merged 1 commit into
developfrom
feat/key-draws

Conversation

@b-re-w

@b-re-w b-re-w commented Nov 9, 2026

Copy link
Copy Markdown
Member

Release address-typing on Chrome after #183-#185 (.scratch\bar-rows-after): Rivet work per key median 14.3 ms, p90 22.7. Per message: key down 3.8 ms, character 8.0 ms (draw 4.2), key up 3.8 ms. Key down and key up still drew, because the text engine's own change report fires for them and bumped the bar's generation.

The draw decision now compares what the bar shows (text, selection, caret, list size, pick, inline completion) before and after the message. Test: nfr2_a_key_that_shows_nothing_new_draws_nothing.

🤖 Generated with Claude Code

…anged

The text engine reports a change for a key down before its character and for a key up, so each
key still drew the bar three times. A message now draws only when the text, its selection, the
caret, the list, its pick or the inline completion changed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@b-re-w
b-re-w merged commit 2accf71 into develop Nov 9, 2026
3 checks passed
@b-re-w
b-re-w deleted the feat/key-draws branch November 9, 2026 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant