You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
It appears the width calculation of each item breaks if the layout gives the masonry smaller available space, and gives it back afterwards. I've detected this with animations using framer-motion, see sandbox below. The masonry container appears to get the correct width. Also, triggering a rerender seems to fix the issue, but i don't know when to rerender in order to fix that.
Thanks for your quick response. Unfortunately, I do not quite get what the proposed solutions are. I thought that the Masonry components use the remaining width automatically, as the masonry container width is set to "100%".
Describe the bug
It appears the width calculation of each item breaks if the layout gives the masonry smaller available space, and gives it back afterwards. I've detected this with animations using framer-motion, see sandbox below. The masonry container appears to get the correct width. Also, triggering a rerender seems to fix the issue, but i don't know when to rerender in order to fix that.
To Reproduce
Hover over the nav bar, in order for it to grow. Then hover away and the masonry stays in the shrunk state
https://codesandbox.io/p/sandbox/frosty-framework-kfksfg
Expected behavior
The layout should adapt to wrapped/unwrapped text and calculate the width accordingly.
Screenshots
Before:
After:
The text was updated successfully, but these errors were encountered: