Windows desktop - Autoscroll needs a toggle!
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What issue are you seeing?
When I send a message, the conversation usually positions my message at the top of the window, leaving the space below it for ChatGPT's response. However, the autoscroll behavior while the response is being generated is inconsistent and often makes reading more difficult.
In one case, ChatGPT starts generating below my message and the page immediately begins scrolling downward with the generated text, even when scrolling is not yet necessary. With longer responses, this causes the beginning of the response to disappear above the visible area. When generation finishes, I have to scroll back up to read the response from the beginning.
At other times, sending my message causes the conversation to scroll upward instead. My message then remains near the bottom of the window, and while ChatGPT generates its response below it, the page does not autoscroll at all. Most or all of the response is therefore generated outside the visible area.
It blows my mind this super obvious issue hasnt been fixed yet.
What steps can reproduce the bug?
Install the standalone and start writing. Duh.
What is the expected behavior?
No response
Additional information
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Start by reproducing the behavior in the standalone Windows desktop app while sending short and long messages, and clarify how the proposed autoscroll toggle should behave. Done means the scrolling behavior is consistent and the toggle's enabled and disabled states are observable.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100