Closed akki-jat closed 5 years ago
Hi, quick thought - change in options timeout to some bigger number https://github.com/karol-f/vue-custom-element/blob/master/README.md#options - destroyTimeout
. This should help.
Please let me know if it solves Your problem.
@karol-f it is not proper solution even if it works, because in real application what number in delayTimeout should I give is uncertain it depends on the user when he wants to come to this component.
What do you say?
You are right. Will look at it.
@karol-f just opened pull request with quick solution. Take a look.
https://github.com/karol-f/vue-custom-element/pull/165 PR is merged - a couple tweaks added:
Just pass null
as destroyTimeout
value and it will work.
Thanks!
Hey @karol-f, When custom element is used in keep-alive then it should not be destroyed but it is getting destroyed and it is causing some wired behaviors (one of them I know is vue $refs are undefined)
Reproduction Link
https://codesandbox.io/s/9y22wqv64
Steps to follow to reproduce the bug
Here is the GIF to better understand the bug