-
Notifications
You must be signed in to change notification settings - Fork 687
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
[css-grid-3][masonry] merge masonry-auto-flow into grid-auto-flow? #10231
Comments
There was once an idea to use the special |
These shouldn't be merged, imo. They're doing the same things, conceptually, but have a totally different set of controls for those things. We'd just have two divergent syntax branches, with one useful only for Grid and the other useful only for Masonry; we'd have to define default behavior for if you used the wrong set of keywords. That doesn't suggest they're actually useful to be in the same property. (This is ignoring the larger issue about Masonry being a different display type in the first place; regardless of that, I think they're still best as separate properties. But if it is a separate display type, they're clearly best as separate properties imo.) (But also, as you say, we can just drop the property entirely if we switch over to |
The CSS Working Group just discussed
The full IRC log of that discussion<flackr> fantasai: now that we've dropped the definite value and the next value, there's nothing for masonry-auto-flow to do, so propose dropping property altogether<TabAtkins> I like a property with no choice in its syntax. `Value: foo bar` , no | anywhere, perfection <flackr> astearns: any concerns about dropping masonry-auto-flow? <flackr> astearns: objections? <flackr> RESOLVED: Drop masonry-auto-flow |
Remove masonry-auto-flow based on the resolution here: #10231
The
masonry-auto-flow
property does something similar togrid-auto-flow
; should we merge these two properties?The text was updated successfully, but these errors were encountered: