Thunberg087 / vue-fragment

a very candide fragment component for Vue.js
http://jsfiddle.net/cdkn5wL3/
670 stars 51 forks source link

Errors on navigation/unloading (v1.5.2) #63

Open web2wire opened 3 years ago

web2wire commented 3 years ago

I've been using 1.5.1 happily for a while but needed to update to use 1.5.2 for the :html binding. Now whenever I navigate (using vue-router) and content is unloaded I get the following.

image

The page does not successfully load. This is in a NuxtJS (2.14.12) environment and the error happens when I am using any fragments on the page whether I actually use the new :html binding or not. If I go back to 1.5.1 the error goes away but my :html bound fragments do not work and so I have to use contained ones which mess up the legacy style definitions I am trying to use.

I will try and create a CodePen but at the moment I'm not really sure how to do routing in CP.

lowbits commented 3 years ago

Have the same issue with nuxt 2.15.3 on two different projects.

stephenjason89 commented 3 years ago

Same here

cyanerd commented 3 years ago

anyone have solution?

web2wire commented 3 years ago

I was able to do everything I needed in the end by migrating to vue-frag as discussed in this issue (https://github.com/Thunberg087/vue-fragment/issues/32)

kwolniak commented 3 years ago

same here on nuxt 2.14.12

lowbits commented 3 years ago

nothing new, think we have to wait for vue3 and nuxt3 so fragment is included. Workaround as @web2wire mentioned use vue-frag, but there you have the problem that the wrapper element is unmounted when page is mounted. Conts classes from parent effects only when page is fully loaded, leads to jumping components

BaileyJM02 commented 3 years ago

This is a duplicate of #32 and can be fixed without changing dependencies. (See #32)

jasonc2901 commented 1 year ago

I was able to do everything I needed in the end by migrating to vue-frag as discussed in this issue (#32)

For anybody experiencing this issue migrating to vue-frag has fixed the problem for me also. Seems this package does not handle conditional rendering very well