-
Notifications
You must be signed in to change notification settings - Fork 841
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
Allow to set a different table-layout #461
Comments
We've gone back and forth on this one a lot. We initially switched back because of an IE issue that cropped up with a max-width hack we were applying. Generally I think tables look best when some, if not all of the column widths are hand applied by the developer. However, that's not really helpful in a lot of your cases since you don't know the data coming in. We've certainly skewed our table thinking more towards layout applications (like management) as of late so the decisions are definitely inflated towards those use cases. I think having a prop for this sounds good so you can switch around as the usage requires it but I think we might stick with fixed as the default simply because it's more generally reliable across browsers. I also want to encourage people to set column widths when they can. I'll try to prioritize this one. |
@andreadelrio Here's an old one to tackle. I think we'd do this by adding a You'll want to make sure this is available on https://css-tricks.com/almanac/properties/t/table-layout/ |
Currently the tables (I think all?) are using
table-layout: fixed
, thus all columns will get the same width by default. This should be configurable for all tables to usetable-layout: auto
instead, which will make the column width automatically be determined. I would even suggest making it the default value, though this might break existing usage, since I think it's the value needed more often, and just in some special cases you actually don't care about the content of the columns and actually want them to be distributed evenly.The text was updated successfully, but these errors were encountered: