-
Notifications
You must be signed in to change notification settings - Fork 75
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
Uncaught TypeError: elem.cloneNode is not a function #74
Comments
I have failed to ozprospect error. You can read more, what were you doing? |
If sweetalert triggered when the page is changing this error will happen. |
Hi @aldarund , Can you provide a code sample with codesandbox.io. Thanks. |
This happened to me when I accidentally passed an Array/Object as a parameter to the message. Now I'm being careful. swal({
message: Array
}) |
2vendors.app.js:43192 Uncaught TypeError: elem.cloneNode is not a function
at handleJqueryElem (vendors.app.js:43192)
at parseHtmlToContainer (vendors.app.js:43178)
at renderTitle (vendors.app.js:43706)
at renderHeader (vendors.app.js:43728)
at render (vendors.app.js:43768)
at MixinSwal._main (vendors.app.js:45227)
at MixinSwal._main (vendors.app.js:43843)
at MixinSwal.SweetAlert (vendors.app.js:45412)
at new MixinSwal (vendors.app.js:43837)
at Function.fire (vendors.app.js:43807)
It could crash whole vue app. Happens when the route changes but vue triggers update at that time and sweetalert triggers. and this error
The text was updated successfully, but these errors were encountered: