-
-
Notifications
You must be signed in to change notification settings - Fork 130
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
table-layout: auto #106
Comments
Two possible ideas:
I think flexbox would be a great fit here. |
@buschtoens a PR is always welcomed 😜 |
@offirgolan What browser compatibility range do you strive for? The flexbox implementation in IE11 is workable but has some considerable bugs as outlined here. I haven't given this any deeper thought yet, but I'll try to cook something up that works in IE11. |
I think this will be an easy solution as of right now.
I would love to see this solution in action @buschtoens but that will take much more time and will need to be discussed further. If you have time to put If you're up to it, can you handle the first solution as an intermediate fix? |
Resolved with #163 via using |
First off, I love Ember Light Table! Much easier than manually creating tables.
I'd like my table to behave like it has the CSS attribute "table-layout: auto". In other words, column widths change to accommodate the width of their contents. But since Ember Light Table renders the table head as a separate table, "table-layout: auto" doesn't consider the width of the body data below.
For example, look at the "League" column (4th from the left). It's wider than the column since Ember Light Table makes all the columns the same width:
![screen shot 2016-07-16 at 8 45 26 pm](https://cloud.githubusercontent.com/assets/20100586/16898078/b983c22c-4b96-11e6-8e16-f5d1cce8afc5.png)
When I give the head and body tables the "table-layout: auto" attribute, the columns become misaligned:
![screen shot 2016-07-16 at 8 49 51 pm](https://cloud.githubusercontent.com/assets/20100586/16898083/eb938eb4-4b96-11e6-9bdd-a79e2e8b68e9.png)
The text was updated successfully, but these errors were encountered: