-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AI scroll-lock suggestions #14362
Comments
@planger WDYT? |
Thanks @dannaf! I agree that the current manual approach isn't enough for a great experience and your suggestion sounds great. What do you about the following minor adjustment -- replacing the suggested behavior on enter to ask another question: |
Yes, I think something like that is probably even better. Ideally there would also be a keyboard shortcut, in addition to a mouse-clickable down arrow. Eg perhaps pressing Enter on a blank question prompt would reengage the autoscroll down? Or double-Enter might be better? Although, actually maybe this is not so critical because if the user 'scrolled up' then the user is already with a hand on the mouse, presimably, so he or she could easily-enough mouseclick the down arrow you mentioned. But I supposed this brings in the additional question of if we want to support page up and page down keyboard shortcuts for scrolling in the AI chat window, this could be good (not sure if that's currently supported, I'm on my phone currently). If there is such support then I would say there should also be a double-enter-or-something keyboard shortcut for reengaging the all-the-way-down scroll, beyond a single page-down button press and without requiring mouse use. |
Feature Description:
While it's nice that the Theia AI chat window already has implemented a scroll lock that can be manually pressed, I suggest that it would be natural and much more useful if, in addition to manual control over it, there would be a default behavior by which the scroll lock is automatically activated when the user scrolls up while an answer is being generated (or any time when scrolling up, due to the next bit) and reengages when the user presses enter to ask another question.
(And there should ideally be an option to not re-engage upon pressing enter, e.g. if the user manually locked, as opposed to automatically locking, then it should remain locked; this might be useful e.g. when want to continue reading one response while meanwhile getting another question asked and generated, without scrolling down to it.)
The text was updated successfully, but these errors were encountered: