-
Notifications
You must be signed in to change notification settings - Fork 0
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
SLVUU-101 improve take screenshot functionality #124
SLVUU-101 improve take screenshot functionality #124
Conversation
Could you add some static images of equivalent screenshots before and after the change, please? It's a bit tricky to evaluate from the gifs. |
vuu-ui/packages/vuu-shell/src/layout-management/SaveLayoutPanel.tsx
Outdated
Show resolved
Hide resolved
vuu-ui/packages/vuu-shell/src/layout-management/SaveLayoutPanel.tsx
Outdated
Show resolved
Hide resolved
child.nodeType === Node.TEXT_NODE || | ||
child.getAttribute("role") !== "row", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These look like good filter criteria to me, but I'd like to know what @heswell thinks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm happy to approve this, but I feel like the styling could be improved where we now have empty rectangles for tables. Perhaps by including a placeholder image to represent a table, and removing the scrollbars.
There is an open BUG tracking this issue on the html-to-image repo. The following changes are aimed at mitigating the issue with the UI freezing when taking a screenshot of a very complex layout
Changes
Before
After
takeScreenshot function throws error (in this case the error is thrown because the layout is not displayed in the DOM)
Note
Filtering out the row elements means we won't be displaying the content of the tables inside the screenshot which could be a positive thing if we are worried about the data being sensitive
fix unit tests