strange behaviors of masonry grid

[wynfred]

strange behaviors of masonry grid

[wynfred]

Not sure about 1, did you try to call layout() after you switch to another category? If you could share a simple repro project, I'll try if I can find what the issue is. One other suggestion I have is try destroy the masonry before you want to reload it completely.
For 2, before the images are loaded they are invisible with opacity 0. If they are clickable, you need to use your own CSS to hide them, and also make sure they are destroyed properly.

[wynfred]

You can use the show/hide animation to set z-index to the items. When I work on the next release I'll make it default as well.

[webcat12345]

It works as charm!!! Legendary!

[webcat12345]

That bug 2, my guess is it's happening when I change ideas (list of items) even there are some pending images to be loaded.

[webcat12345]

That makes sense your comment on issue 2. I can see opacity 0 div is there. But I can't find the best approach to disable click event for all of those opacity 0 divs. Do you have any guidance to give me? I don't see any additional classes added to un-aligned elements (those opacity 0 elements)...

Issue 1, I will try to call layout() function from my side, I will come back after some tries.
Thank you!

[webcat12345]

By calling the layout() function on category change event, I was able to figure out that issue 1. Not that perfect but it's working.

So, sometime, very barely column shows as 1. But if I change category it's getting recovered because I am calling the layout() function. So I would say issue has been resolved. Just trying to find out best way to handle issue 2, please let me know if you have any hint. Thank you!