There are a few old issues that mentioned this problem and I have found it myself when transitioning between routes in my app.
The problem is that masonry.destroy() is called immediately when components begin to destroy themselves on a page. This causes an issue during route/page transitions because all items will be aligned left in a single column (masonry is destroyed while the element is still visible during the transition).
With this addition you can set the amount of milliseconds you wish to wait for a destroy in the destroy-delay property on a vue-masonry element.
Fixes #77 for @nicroto and the issues users @treardon17, @kotuck, @max-schu, and @mklasinc were discussing in #48.
There are a few old issues that mentioned this problem and I have found it myself when transitioning between routes in my app.
The problem is that masonry.destroy() is called immediately when components begin to destroy themselves on a page. This causes an issue during route/page transitions because all items will be aligned left in a single column (masonry is destroyed while the element is still visible during the transition).
With this addition you can set the amount of milliseconds you wish to wait for a destroy in the
destroy-delay
property on a vue-masonry element.Fixes #77 for @nicroto and the issues users @treardon17, @kotuck, @max-schu, and @mklasinc were discussing in #48.