Hard to read while generating response
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
### Short summary
Output text is hard to read while generating response because of ticking output
### Affected version or release
v1.0.17
### Installation context
macos desktop app
### What happened?
I would like to share some feedback regarding the scrolling behavior during response generation.
When I prompt the system and receive a response, the text streams (tickers) downwards. If I start reading the response while it is still generating, the continuous scrolling makes it very difficult to read.
To prevent this, I try to scroll up slightly in the hope that it will freeze the scrolling. However, the window continues to auto-scroll. This means I cannot actually start reading until the entire output is finished generating.
I would highly appreciate it if you could improve this interaction: once a user manually scrolls up while an answer is being generated, the system should detect that the user wants to start reading, stop auto-scrolling, and keep the view stable.
### Steps to reproduce
1. Prompt something with a long response
2. Try to read it
3. Observe that the output text is moving as more text is generated
### Expected behavior
Freeze scrolling when observing that user intentionally scrolls upwards to read the text.
### Additional context
_No response_
Contributor guide
Research direction
Start in the macOS desktop app's response-generation view and reproduce the behavior with a prompt that produces a long response. Observe what happens when the user scrolls upward while text is streaming; done means upward scrolling stops auto-scrolling and keeps the view stable until the user chooses to move it.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100