Weird bug causing portal component losing all states & refs

[nodegin]

See the bug in action

This seems is a portal-vue internal bug, currently I am using the display hack as workaround.

In case codesandbox link dead:
vue-portal-slots.zip

[nodegin]

Another interesting behavior: if you edit Vuex store state smallScreen to true

The bug will be deferred for 1 tick

demo

[LinusBorg]

Hm, interesting.

My first suspicion would be that the same vnodes are re-used when switching from one portal-target to the other, but since they were already used to be mounted in the first target, they don't work correctly in the second one.

But if that was the case, a scoped slot instead of a normal one should solve it, but doesn't either.

Will look into it further.

[LinusBorg]

Hey @nodegin I just published 1.5.1-beta.0, you can install it with the next tag:

npm i portal-vue@next

Please test this version and report back if your issue is fixed - it should be.

[LinusBorg]

Nevermind, this path release won't fix it either. In fact, after taking a second look I think there's not much we could do.

In the part of your example that is the "bug", you are, by using v-if, destroying the portal and all of its children - which included the stateful component.

And in the other target that you are switching to, the component has to be re-created.

There isn't really anything we can do about this, I think. Sorry.