You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the new Dropkick(elem, {mobile: false}) configuration, DropKick will crash when calling methods that manipulate Dropkick like .refresh() and .dispose() on mobile. DropKick will attempt to remove itself even though it was never mounted causing an error.
The hack fix I found was to check that dropkick.data.elem.parentNode has a value before calling any of the DropKick functionality. This check should probably be added to DropKick before performing DOM manipulations or offer a function for users to easily check if DropKick was actually mounted.
The text was updated successfully, but these errors were encountered:
When using the
new Dropkick(elem, {mobile: false})
configuration, DropKick will crash when calling methods that manipulate Dropkick like.refresh()
and.dispose()
on mobile. DropKick will attempt to remove itself even though it was never mounted causing an error.The hack fix I found was to check that
dropkick.data.elem.parentNode
has a value before calling any of the DropKick functionality. This check should probably be added to DropKick before performing DOM manipulations or offer a function for users to easily check if DropKick was actually mounted.The text was updated successfully, but these errors were encountered: