Skip to content
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

[Bug] Performance degrades for large DOM trees #135

Closed
Kitenite opened this issue Aug 8, 2024 · 1 comment · Fixed by #312
Closed

[Bug] Performance degrades for large DOM trees #135

Kitenite opened this issue Aug 8, 2024 · 1 comment · Fixed by #312
Labels
bug Something isn't working

Comments

@Kitenite
Copy link
Contributor

Kitenite commented Aug 8, 2024

Describe the bug

There's a lot of DOM processing happening which makes editing slow for large,nested DOM trees.

Try with example:
https://www.google.com/search?sca_esv=f34a7ccbd9a4492c&sca_upv=1&q=sport+climbing+combined+olympics&oi=ddle&ct=348045702&hl=en&sa=X&ved=0ahUKEwi4_Pys7OWHAxWqFlkFHVwPFvQQPQgC&biw=1362&bih=823&dpr=1

@Kitenite
Copy link
Contributor Author

Kitenite commented Aug 21, 2024

This is isolated down to the user of getDeepElement and how when using with deep nested DOM it can have a large performance hit

@Kitenite Kitenite linked a pull request Sep 13, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant