web: auto-scroll streaming edits with sticky-bottom#12
Merged
Conversation
edits during streaming now scroll the messages container to the bottom when the user is within 64px of it, matching standard chat ux. scrolled-up readers stay put.
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
editMessageTextevents in the web UI no longer require manual scrolling — the messages container now follows the bottom while the assistant generates output.Why
The web UI bridges the same content stream Telegram gets, but Telegram's transport hides the issue (push edits are invisible until you open the chat). On the web, an open viewport made the lack of auto-scroll obvious — every streaming edit grew the body off-screen.
Test plan
@write a 30-line poem), confirm the view follows the bottom as the response streams.