-
-
Notifications
You must be signed in to change notification settings - Fork 32.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Masonry] Ability to sort elements from left to right #36859
Comments
any updates? |
1 similar comment
any updates? |
please? |
@hbjORbj Can you take a look? |
Yeah- seems like it orders items like-
Unless I'm doing something incorrectly, but- the way it works right now makes it very difficult to use masonry with any sort of infinite scrolling- as it would result in things being completely rearranged. I hope there's a simple fix for this and that I'm completely wrong- but as it is, it's not very convenient for most use cases. |
Hi @Whitelistedd, thanks for the report, and sorry for the late reply One of the initial requirements for the Masonry component was that items should be placed in the shortest column available, so "by design" it disregards the order they are provided. It would be nice if we could deactivate this for the use case you report, so if you (or anyone) would like to work on a PR, that would be great 😊🚀 |
I've started implementing it over here: /~https://github.com/Rishi556/material-ui/tree/sequential-columns if anyone wants to follow along i've got a draft PR up #39904. I've got an eslint error to resolve and some tests to add, but maybe I'll be able to PR it in on Monday. |
Duplicates
Latest version
Summary 💡
The ability to sort Masonry elements from left to right instead of top to bottom where it just fills any spot instead of force sorting from left to right
Examples 🌈
I am assuming this is how it works right now maybe I am wrong
Motivation 🔦
I need to sort hotel cards from most expensive to less expensive and its not really displaying the order correctly
The text was updated successfully, but these errors were encountered: