Repository navigation
fix(web): keep thread annotation typing responsive - #173
Merged
Merged
Conversation
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.
The thread annotation editor re-rendered its complete dialog subtree on every keystroke and continuously recalculated the textarea's intrinsic height. This made typing noticeably laggier than the composer.
Keep the draft in the native textarea, update React state only when Save eligibility changes, and use a fixed-height internally scrolling editor. In an integrated browser check, 2,000 input events completed in about 73 ms with one expected UI mutation; the textarea remained 208 px tall.
Validation:
Implemented with GPT-5.6-Sol through the Codex harness.