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.
What was happening
The log viewer currently offers two separate modes: auto-follow and manual scroll.
In practice, this causes frequent UX issues:
This results in a frustrating experience when inspecting long or fast-updating logs, especially during running pipelines.
Related issue
Closes #5971
What this PR changes
This PR simplifies log following behavior by making it scroll-position aware instead of mode-based.
Why this approach
Scroll position is the most reliable signal of user intent.
Previously, auto-follow was controlled by explicit modes, which required constant manual interaction and were easy to forget.
By deriving auto-follow state from the scroll position:
Implementation overview
sequenceDiagram participant User participant UI as Log Viewer participant Stream as Log Stream Stream->>UI: new log lines UI->>UI: check scroll position alt user is at bottom UI->>UI: autoFollow = true UI->>UI: scroll to bottom else user scrolled up UI->>UI: autoFollow = false UI->>UI: preserve scroll position end User->>UI: scrolls back to bottom UI->>UI: autoFollow = trueTests
No automated tests were added.