Closed downhiller closed 5 years ago
I just came across this particular issue. The breakpoints are useless in my scenario. Priority 1 doesn't fit the largest breakpoint, so I'm at a lost.
I'm thinking about implementing it myself, or setting up a PR.
This is an interesting idea. I think I like it.
Just for @veksen’s sake priority 1 is the smallest min-width. See this:
I have implemented this code in my own project now. When I get a chance I'll try to clean it up for you, should you be interested.
@downhiller I am interested for sure!
Maybe next week, I'll add it to my todo list.
This repository is now using lodash style issue management for enhancements. This means enhancement issues will now be closed instead of leaving them open.
The enhancement backlog can be found here: https://github.com/filamentgroup/tablesaw/issues?utf8=%E2%9C%93&q=label%3Aneeds-votes+sort%3Areactions-%2B1-desc+
Don’t forget to upvote the top comment with 👍!
I see at the moment there's 7 priority levels (persist & 1-6). And that each level is set to a CSS breakpoint.
That can seem a bit arbitrary, especially on a dynamic website where the content of the columns can vary a lot.
What I'd like to see would be a more fluid approach.
1) instead of 0 & 1-6, any float can be applied to priority: 0, 1, 1.1, 1.2, 2, 3, 30, 200, etc.
2) the table is then displayed initially with "0" only. The next priority (in this case 1) is added. Then 1.1. Then 1.2. Then 2. Etc etc. Until the table runs out of space to display columns.
This would give an intelligent auto-fit.
It's not so important if you have wrapping in your table cells, but if you're trying to avoid wrapping I think this would be a very useful/important feature for some people.
Do you have any plans to add such functionality, or am I on my own? :-)
Thanks!