vue-fragment icon indicating copy to clipboard operation
vue-fragment copied to clipboard

Errors on navigation/unloading (v1.5.2)

Open web2wire opened this issue 4 years ago • 8 comments

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.

web2wire avatar Mar 12 '21 15:03 web2wire

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

lowbits avatar Mar 19 '21 09:03 lowbits

Same here

stephenjason89 avatar Mar 24 '21 16:03 stephenjason89

anyone have solution?

cyanerd avatar Mar 29 '21 07:03 cyanerd

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)

web2wire avatar Mar 29 '21 07:03 web2wire

same here on nuxt 2.14.12

kwolniak avatar Mar 30 '21 17:03 kwolniak

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

lowbits avatar Apr 06 '21 08:04 lowbits

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

BaileyJM02 avatar Apr 29 '21 10:04 BaileyJM02

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

jasonc2901 avatar Sep 16 '22 14:09 jasonc2901