-
-
Notifications
You must be signed in to change notification settings - Fork 159
Possible DOM memory leak? #302
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
Labels
bug
Something isn't working
Comments
@lightwalker01 Nice catch, thank you for reporting this After some investigation, discovered that the actual cause for this are SVG icons. Will need to investigate a little why this is happening. |
@Jasenkoo I thought it was because of “click outside” directive or something like that… |
Closed
Jasenkoo
added a commit
that referenced
this issue
Mar 15, 2025
Jasenkoo
added a commit
that referenced
this issue
Mar 15, 2025
Jasenkoo
added a commit
that referenced
this issue
Mar 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
When VueDatePicker component is added to and then removed from DOM, many detached objects remain even after GC.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
There are no DOM detached objects
Desktop & mobile (please complete the following information):
The text was updated successfully, but these errors were encountered: