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
Uncaught TypeError: this.context is null
onDragUpdate vuedraggable.js:266
tt vuedraggable.js:20
et vuedraggable.js:28
G Sortable.min.js:2
V Sortable.min.js:2
_onDrop Sortable.min.js:2
handleEvent Sortable.min.js:2
h Sortable.min.js:2
_onDragStart Sortable.min.js:2
h Sortable.min.js:2
_triggerDragStart Sortable.min.js:2
o Sortable.min.js:2
_prepareDragStart Sortable.min.js:2
_onTapStart Sortable.min.js:2
Expected Solution
Dragging works normally.
Notes
Vuedraggable appears to assign __draggable_context before the async components have resolved and mounted, so it gets put on a placeholder comment tag that Vue later removes, leaving no reference to the real element. I think the same thing would happen with a dynamic component or a custom async loader.
This only happens if the async component is the root of the item slot, so it's fairly easy to work around by wrapping it in a div, once you know what's wrong.
The text was updated successfully, but these errors were encountered:
First check https://github.com/SortableJS/Vue.Draggable/blob/master/CONTRIBUTING.md
I couldn't find details on what versions of sortablejs were compatible, and the link goes to Vue.Draggable for Vue 2. I used the most up to date versions of each library, instead.
Jsfiddle link
https://codepen.io/wartmanm/pen/OJKRWyM
Step by step scenario
Actual Solution
An internal error in vuedraggable occurs:
Expected Solution
Dragging works normally.
Notes
Vuedraggable appears to assign __draggable_context before the async components have resolved and mounted, so it gets put on a placeholder comment tag that Vue later removes, leaving no reference to the real element. I think the same thing would happen with a dynamic component or a custom async loader.
This only happens if the async component is the root of the item slot, so it's fairly easy to work around by wrapping it in a div, once you know what's wrong.
The text was updated successfully, but these errors were encountered: