Release v0.51.591 — Release UX (stop transcript jumping to first message, #4721/#4720)
This commit is contained in:
parent
44d840d0a1
commit
35412fd3ef
1 changed files with 2 additions and 0 deletions
|
|
@ -3,6 +3,8 @@
|
|||
|
||||
## [Unreleased]
|
||||
|
||||
## [v0.51.591] — 2026-06-22 — Release UX (stop transcript jumping to first message on completion)
|
||||
|
||||
### Fixed
|
||||
|
||||
- **The transcript no longer jumps to the first message after every completion.** On a long conversation that loaded truncated, finishing a turn snapped the viewport to the top. The `done` event replaced the transcript with the full payload and expanded the render window to all messages, but left `_oldestIdx` stale — so the absolute scroll anchor (introduced with the read-position work) resolved to the wrong row and the view jumped to the start. The completion handler now resets `_oldestIdx` from the payload exactly like the other full-load paths, keeping the reader anchored where they were. Pinned-at-bottom readers still follow to the latest message. (#4720)
|
||||
|
|
|
|||
Loading…
Reference in a new issue