You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey everyone, I have been working on a project that uses the library and its pretty cool. Mostly we are using the data-tables and there are quite a lot of them with the same styling and similar ish structure, they are generated based on the data given and takes up quite a bit of the application.
One thing that is common for them as of right now is they are all user resizable and that does work great.
Our users are requesting that the columns would on load be as small as possible based on the content in them, but still be resizable.
I have been lead to understand the table-layout needs to be fixed to not get any problems with resize functionality - thus the width interface attribute can't be dynamic in nature akin to something like "fit-content" or similar css styling
Have I completely missed or misunderstood something? Has anyone had similar issues and come up with solutions?
the width of the container itself is filling out the space so that the table is the desired size, but we do tend to have a lot of columns in some of the tables making dynamic sizes for the columns very attractive for the users as they then might not need to resize as much
Let me know if this confusing and I will try to clarify
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey everyone, I have been working on a project that uses the library and its pretty cool. Mostly we are using the data-tables and there are quite a lot of them with the same styling and similar ish structure, they are generated based on the data given and takes up quite a bit of the application.
One thing that is common for them as of right now is they are all user resizable and that does work great.
Our users are requesting that the columns would on load be as small as possible based on the content in them, but still be resizable.
I have been lead to understand the table-layout needs to be fixed to not get any problems with resize functionality - thus the width interface attribute can't be dynamic in nature akin to something like "fit-content" or similar css styling
Have I completely missed or misunderstood something? Has anyone had similar issues and come up with solutions?
the width of the container itself is filling out the space so that the table is the desired size, but we do tend to have a lot of columns in some of the tables making dynamic sizes for the columns very attractive for the users as they then might not need to resize as much
Let me know if this confusing and I will try to clarify
Beta Was this translation helpful? Give feedback.
All reactions