You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When Prompta is streaming a long response, it is currently necessary to wait until the whole response has been streamed before one can begin reading from the top as, despite manually scrolling to the top, the client repeatedly scrolls back down to the bottom with each additional piece of response added.
This is not a show-stopper at all, but it is mildly frustrating as one has to wait until the response is finished before one can start reading (and knowing that one's reading speed is much slower than the speed at which the response is being written, this shouldn't be a problem.
Please arrange that, once the user has manually scrolled up from the bottom, the client will not reset the scroll position as the response is being streamed. This behaviour would be consistent with e.g. Mac OS Terminal.
The text was updated successfully, but these errors were encountered:
Must be a bug. I added this when first creating prompta but haven't revisited in a while. it also never worked very well (at all?) on mobile safari if I remember correctly. The code in question uses this function:
When Prompta is streaming a long response, it is currently necessary to wait until the whole response has been streamed before one can begin reading from the top as, despite manually scrolling to the top, the client repeatedly scrolls back down to the bottom with each additional piece of response added.
This is not a show-stopper at all, but it is mildly frustrating as one has to wait until the response is finished before one can start reading (and knowing that one's reading speed is much slower than the speed at which the response is being written, this shouldn't be a problem.
Please arrange that, once the user has manually scrolled up from the bottom, the client will not reset the scroll position as the response is being streamed. This behaviour would be consistent with e.g. Mac OS Terminal.
The text was updated successfully, but these errors were encountered: