Tag Info

New answers tagged

2

Here's a more condensed version of what you posted. I kept the read-only fields on a row separate from the inputs you can actually alter.


0

I just did the same as nightning when I had to bring a table (only 6 columns) into a 320 px version for mobile users. My first move was to delete all the columns that had information the user wouldn't actually need. It was just given, because... well, because obviously. So there are only 4 columns left. It flips to column again for tablet users and above, ...


2

Tables are soooo 90s (they are about to turn 30) HTML tables were proposed in 1993 and took off around 1996. During this time, few considered accessibility and even less predicted responsive design. UX was never considered in the process. This case isn't unique, there are many other HTML standards that nowadays look ludicrous - selects and radio groups all ...


2

It is interesting to me that the problem with large multi-column tables is not being solved by creating better content and information architecture, because regardless of how responsive or accessible the table is the information is still going to be unusable to the reader if there is simply too much information. The question of how to fit a large amount of ...


5

Hmmm take a look at this: https://github.com/filamentgroup/tablesaw As width is reduced, the table converts over into a listing. You do lose the ability to do row comparisons, but it does ensure data remains accessible for small screen sizes.



Top 50 recent answers are included