The buttons on the bottom of a thread (copy, regenerate, info) shouldn't be inactive depending on how far you scrolled

chris_20017

The buttons on the bottom of a thread (copy, regenerate, info) shouldn't be inactive if you did not scroll far enough. As long as the down arrow is visible, they are not actionable.

Visible interface elements shouldn’t be activated or not depending on visual gimmicks like the fade in effect at the bottom of a thread.

terry

The gradient blocks text selection, harming the user experience. I try to copy the text countless times and I can't because of this <div> that is above the text. I always have to scroll first to then copy, even though the information is already on the screen.
Using print as an example, it is impossible to copy the "however" paragraph. It is necessary to scroll first and then copy.

I would like to be able to select and copy any block of text or code that is appearing on the screen
An alternative would be to just leave the arrow above the text, or even move the arrow perhaps to the left above the model selection?

Luis

terry merging with a similar thread to streamline communication