-
Notifications
You must be signed in to change notification settings - Fork 14
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
Restriction on Copying and Scrolling #69
Comments
This is an interesting problem, because since the log viewer is vitrtualized, it is only rendering the visible text in the DOM - there is no other text to copy. It might be that a button should be added to the log viewer's toolbar which adds the whole content in the stream to the clipboard? |
I have a string of data separated by new lines and an overscan count of approximately 60. Initially, all lines are present in the DOM, and with the overscan count, I expect to copy at least X lines. |
hm... yeah using the |
Hi @nicolethoen, Has the issue been resolved in version 5.3.0? Do we need any extra props to be added? |
Hi @nicolethoen, do we have any new updates? |
I don't currently have an update. We haven't had a lot of resources to investigate the log viewer issues super recently. But it still has a P1 tag, so as soon as we do, this is toward the top of the list. |
Description
The log viewer component currently prevents users from scrolling down while copying text. Consequently, only the text visible on the screen can be copied, making it impossible to copy the entire log or reach certain lines that are not initially visible.
The copying and scrolling work with key controls but not with the mouse.
Steps to Reproduce
Expected Behavior
It should be possible to copy and scroll down the text within the log viewer up to a certain limit, including lines that are not initially visible.
Actual Behavior
Copying is restricted to the text visible on the screen, preventing the entire log text from being copied, including lines that are not visible.
Environment
Screenshots
The text was updated successfully, but these errors were encountered: