Skip to content
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

Columns implementation : why grid [only] and why columns are not wrapped/separated? #7396

Closed
eddr opened this issue Jun 20, 2018 · 2 comments

Comments

@eddr
Copy link

eddr commented Jun 20, 2018

Hi

Why a grid was selected to be the base for columns? I think it can be limiting and uncomfortable in some situations, especially when responsiveness it needed. Also, the fact the columns are not wrapped with div or something could result in some unnecessary complications

For example:

  1. A flexbox would allow automatic wrapping, making it much easier to handle responsiveness in most cases
  2. with unwrapped columns (as it is now), inner elements are artificially aligned - this is an unwanted behavior many times.

I understand that with grid and "soft" columns the ability to order is maximized and that in some cases (probably not that many), it would be beneficial.
However, it is not as advantageous for most as flexbox, so at least it might be a good idea to implement a choice between grid and flex + "hard" columns. Should be hard, after all and allow for a better control and less work.

@rickcurran
Copy link

Yep, a few people (including myself!) are keen for improvements here. This PR is worth following: #7234

@mtias
Copy link
Member

mtias commented Jun 22, 2018

There's multiple conversations around this. Closing so we can focus discussion in #7234

@mtias mtias closed this as completed Jun 22, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants