Repository navigation
Conversation
…olls up The chat decided on every streamed update whether to follow the tail by distance from the bottom: within 160px, jump to the bottom. One wheel notch is about 100px, so the first move up still counted as "near the bottom" and was undone on the next frame; the reader had to out-scroll the stream to read anything above it. Follow is now decided from the reader's scroll events (lib/opencode/scroll-follow.ts, unit-tested): any move up leaves it, a clamp from shrinking content does not, and scrolling back near the bottom rejoins. Sending a message or switching conversations rejoins too, and a sticky "Jump to latest" / "Follow the reply" button appears while not following. Refs #678
fix(chat): stop following a streaming reply as soon as the reader scrolls up
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.
Promotes the following, merged into
developafter #677, to main.Closes #678
Closes #681
Included:
lib/opencode/scroll-follow.tswith unit tests.6.0.0.dev0to6.0.0.dev1(Dockerfile). Pin the image to Pegasus 6.0.0.dev1 #681 records it.CI on the develop head (5302af3) is green: pytest, tsc, vitest, image build.
Merging this publishes
:main, which production pulls on the next pod restart.Not yet checked by hand on
:develop:pegasus-versionin a fresh pod reports 6.0.0.dev1, and the/etc/pegasus/pegasus.propertieslink from fix(build): link /etc/pegasus/pegasus.properties into the planner's sysconfdir #676 still lands in the new package'ssysconfdir.Not covered: hosted runs are planned on the AP, so the AP's own Pegasus version (salt, studio-system) is what plans them, not the image's.