Could you create a jsfiddle?

Vue component are also supported so this linked to your specific example.

See the following example:

        <v-layout row wrap>
          <v-flex
            v-for="(row, i) in rows"
            :key="i"
            xs12
          >
            <v-card>
              <draggable
                :value="rows"
                tag="v-layout"
                class="row wrap fill-height justify-space-around align-center"
                ghost-class="draggable__ghost-class"
                :group="{ name: 'actionRows' }"
                @input="onChangedRows($event)"
              >
                <v-flex
                  v-for="(item, itemIndex) in row"
                  :key="itemIndex"
                  class="action-plan__action__row__edit dropitem"
                  xs12
                >
                 <!-- div WORKS -->
                  <div style="min-height: 100px; background: brown">TEST</div>
                 <!-- but v-card and other vue components trigger the ERROR -->
                  <v-card style="min-height: 100px; background: brown">TEST</v-card>
                </v-flex>
              </draggable>
            </v-card>
          </v-flex>
        </v-layout>

Does this help or do you need more to dig into it?

Not really.
I can not debug without jsfiddle.

Note that you need to use or list or v-model.
value prop without updating the list on input will not work

Sorry, it somehow did not copy the @input. That mechanism actually works. I'm also figuring out how to setup the right jsfiddle in the meantime though.

@David-Desmaisons I created a jsfiddle including some examples:

https://jsfiddle.net/lexixon/nf97erqx/64/

I think I have narrowed down the issue. It occurs whenever there is only one item left within a draggable section and you try to move it and it depends whether it was dynamically added or not (see all examples in jsfiddle). Potentially it has something to do with the nesting but I hope there's a simple explanation what triggers it and how to prevent it.

Error:

Uncaught TypeError: Cannot read property 'element' of null
    at VueComponent.onDragStart (vuedraggable.js:380)
    at mt.<anonymous> (vuedraggable.js:37)
    at Ct (Sortable.min.js:3)
    at mt._dragStarted (Sortable.min.js:3)

@David-Desmaisons or anyone else any idea what I'm doing wrong or how the issues in the illustrated examples can be explained?

@alexeigs , I am investigating, this is something that can be correct on vue.draggable side.
Currently as a by-pass you can use a div with the required class instead of a v-layout and it will work.

I've had the same issue with this error popping up when reordering nested properties.
I can confirm that wrapping my Vue component in a <div> fixed the error.

So for example, the following HTML code:

<draggable :list="page.children" v-bind="dragOptions">
    <transition-group name="list" tag="ul" v-if="hasChildren(page)" class="children">
        <menu-node :active-page="activePage"
                              v-for="child in page.children"
                              :page="child"
                              :key="child.id">
        </menu-node>
    </transition-group>
</draggable>

had to be replaced by:

<draggable :list="page.children" v-bind="dragOptions">
    <transition-group name="list" tag="ul" v-if="hasChildren(page)" class="children">
        <div v-for="child in page.children" :key="child.id">
            <menu-node :active-page="activePage" :page="child">
            </menu-node>
        </div>
    </transition-group>
</draggable>

@David-Desmaisons @Shammah

How would that work in my case exactly to transfer the full v-flex class on the div and let the v-layout and v-flex behave in the same way? Could someone share that bit of code?

What worked in my case was to move the v-for out of my Vue component and into a <div> one layer up. So in your case that would be

<draggable :value="rows"
           tag="v-layout"
           class="row wrap fill-height justify-space-around align-center"
           ghost-class="draggable__ghost-class"
           :group="{ name: 'actionRows' }"
           @input="onChangedRows($event)">
  <div v-for="(item, itemIndex) in row" :key="itemIndex">
    <v-flex class="action-plan__action__row__edit dropitem" xs12>
            <v-card style="min-height: 100px; background: brown">TEST</v-card>
    </v-flex>
  </div>
</draggable>

I hope this fixes the issue for you as well.

@Shammah The issue is that this will break the dependency of v-layout and v-flex. The flex boxes will not behave anymore as they do being directly nested in the layout which actually has been my challenge in finding a workaround for this issue.

Hmm, I thought I fixed it, but it seems to have only solved a few of my cases. I now get the same error, even when wrapping in a div. My use case to reproduce:

1. Start with an array with one element.
2. Add a nested child to that element, thus the original element will become a parent.
3. Move the child out of its parent.

The error does not happen if you start with an already existing list that contains both parent and child nested.

My colleague found a fix, by simply forcing a Vue rerendering when the amount of children change. This is achievemed by supplying a :key to the draggable.

<draggable :list="myArray" :key="myArray.length"></draggable>

Does this work for you as well?

I noticed that the :key thingy was also applied to the <div> in my previous post, which is why I thought that the div itself fixed some of my cases.

Edit:
In your case that would be

<v-card>
    <draggable :value="rows" :key="rows.length">

Corrected in version 2.22.0