It's probably worth including the thead and tbody. A sticky thead is great for big tables and/or small screens.

Жыл бұрын

I thought the same with the sticky thead. I think that github does it when viewen large files and it's very usefull. Also tbody tag I always asumed that browser puts it if you forget it, but maybe was just my imagination.

@mityukov

Жыл бұрын

Arghhh... Those sticky headers are a bitch to implement. Especially, if you're table is horizontally scrollable. Would love to see a couple of decent solutions for this

@404-UsernameNotFound

Жыл бұрын

table tr:first-of-type { position: sticky; top: 0; }

@daguttt

Жыл бұрын

@@404-UsernameNotFound This doesn't work as-is

@marklnz

Жыл бұрын

Regardless of the need for a sticky header, thead and tbody are surely the correct way to define a table semantically?

This is exactly what I was looking for for the last 2 years! THANK YOU!

Kevin providing the knowledge once again! You're a life saver sometimes with the videos you create. They always seem to come at just the right time!

What a fabulous tutorial on tables. I’m really grateful for this. Thanks for working your CSS magic Kevin.

This is absolutely amazing! Been needing this and am so glad you decided to cover it -- thank you so much!!

Kevin, thank you for what you do! You taught us a lot for past few years! I felt in love with css and built my thinking process on how to build responsive layouts! Thank you very much! However, community demands part 2.

Your solution is great. I usually use the overflow one because most of the time data presented in tables is viewed on larger devices but now that I know that it's as easy and straight forward as this, I don't have to rely on a UI framework to handle tables. Thank you.

A video about responsive . Kevin, you are a hero. You could have mentioned the scope attribute also, but it is explained well in Adrian's blog posts. Thank you.

As someone who still does newsletters the old fashion way (coding them myself, using tables), I love the fact you’ve adresses this subject !

Your video couldn't have arrived at a better time: I'm just finishing an API whose data needs to be displayed in a table. Your video helped me a lot. Thank you so much!

instead of using the data-cell attribute, I would advocate for the use of headers attribute, which accepts a space separated values of the ids of the s that describes the cell. not only it can be used in the attr() function but with a small css/javascript you could add some cool functionalities to highlights specific cells of the same headers. on complex tables, it is common to have row and column headers, even group headers for a particular set of rows and columns, for those scenarios, and are also a good addition to the table markup

@dealloc

Жыл бұрын

Not only that but it also makes it more accessible. Data attributes and "content" properties are not accessible as they are not part of the markup. While some assistive technologies may announce content in before/after psuedo elements it's best not to rely on this because it depends on the tool and user's settings. Given that before and after are mostly used for decorative purposes, these are often disabled by default, if at all.

@wayneswildworld

Жыл бұрын

​@@deallocWhat do you mean by not accessible?

@dealloc

Жыл бұрын

​@@wayneswildworld As in screen readers does not read data-attributes and often not decorative content on pseudo elements. They are not visible in the accessibility tree.

@wayneswildworld

Жыл бұрын

@@dealloc aaaah I understand! thanks for taking the time to respond!

@gabydewilde

Жыл бұрын

@@wayneswildworld cant use the clipboard either

I have been looking for a simple approach like this. I was struggling a little with creating a responsive solution for data that was best put in a table, while keeping it accessible. I really like these solutions.

Another approach that is more mobile-first is to start with a and style it with table attributes on larger screen sizes. Unfortunately, you still need a bit of extra markup to do the table heading.

Great content as always. I remember that in this full stack MERN project I developed, I had to implement responsive tables as a functional reusable React component. I had like 4 or 5 tables in that website. I remember I used a base code from Codepen but I had to change several things in it as well and add others. It drove me nuts but I got it done. It was worth it. 👍

A great intro to responsive tables and a lot simpler than I imagined. As for adding data-cell="column heading", I generate most of my tables either through PHP or Javascript so that's pretty easy to add to the template, in this case a JS template string: `${data[field]}` The site is multi-lingual, hence the curLang[field] item.

You are single handedly getting my through my Diploma. Thank god you exist my friend!

Thank you, Kevin! You're like Joda CSS master. Be healthy and successful!

WOW. This is a gold mine. Thanks a lot Kevin. Am sure you will receive a lot of love because this has been a wish for many people.

I have known the era of « layout with table » too. CSS was not the same during the Jurassic !

@precisionchoker

Жыл бұрын

I once had to design some email templates and I was grateful for modern CSS

@LastRoseStudios

Жыл бұрын

@@precisionchoker That's why I avoid doing email templates

@ClaudioBrogliato

Жыл бұрын

I feel you. Still a pain nowadays with email templates.

@bojancenikol

Жыл бұрын

I was there Gandalf, 2000 years ago

@evanevan5096

Жыл бұрын

​@@precisionchoker😊

Oh THANK YOU KEVIN! I've struggled a bit with this because at some point you do just need to break the table into stacks or grids or something and the way tables work is just WEIRD. The question was what to do with it once you decide you've gotta break from table to something else, and what precisely that something else should be. Grid is obviously the solution, and while you used it to simply stack everything, you could come up with more complex layouts at a couple different screen sizes to account for e.g. desktop, tablet, and phone. I had an idea what doing this right might look like, I just needed to see the pieces assembled, so thank you for doing that!

Your all videos are worth to add in my youtube library for future references

Thank you so much Kevin! This is exactly what I needed, I left a comment on some previous video asking for this topic. Much appreciated!

I’m building a sports website (including F1) for my portfolio right now and I’m having a little trouble with the tables so this video is quite relevant to my interests 👍🏽

It's Amazing! So simple and so workable. Thank you!

I know this "trick" from the default OutSystems Styles. Tables behave there like this too. I'm not thaaaat happy with the table result, but i think that's all you can expect from an easy and fast responsive approach. Great that you made it public!

Love this so much Kevin... Always had to run to grid when to deal with it.. Thank you so much

This is awesome and very helpful. Thanks Kevin keep up the great work.

Kevin, this is Awesome. I'm so glad I found your channel! Loving pretty much every video you put out!

What a brilliant tutorial. Hits the mark perfectly and easy to follow. Thank you.

your videos are awsome!!! learning a ton with them! Thank you kind sir

You really should use and elements within the table around the respective sections.

To me you are a CSS magician, all those commands you do out of your head. I make a lot of use of Bootstrap, but that reacts sometimes so weird. More and more i think i have to go back to basic CSS. Very good info on making a table responsive, thank you for sharing.

Terrific ideas beyond the container overflow-x trick, which is what I have usually gone to. Thanks!

thank you veryy much ,it's delivered at the right time ,i need it now ,thx mate

thanks so much for making this video - great solution for a responsive table.

just implemented this into our ticket-tracking system and people love it!

Great video! Thanks!

This really helped me beef up my final, thank you!!

Fantastic fix for responsive table...the bain of my life!

Thanks so much, now I can complete my responsive table project.

Thank you, Kevin! This is a great solution!

Wow I didn't know that! Awesome! Thank you!

Oh man!! Responsive tables can't b more simple 😎, awesome 👍

Ah yes, my favourite F1 driver Rico Rosberg. PS. Another awesome video Kev, keep rocking ❤️

Fantastic ! A big thank-you

Awesome video, very helpful. The data-cell attribute approach works for me because I create tables dynamically in code.

Thank you alot, so simple but very effective solution.

I never knew about using attributes in css, that's really cool

great and very helpful ... as always

Thank you for this valuable video! Kevin, it is the best solution for my project!

Friend, that was great. Thanks !!!!

Always great content!

Really inspired by this video. Thanks.

I've always had problems with tables, but this helps Kevin thanks

Tables are the bane of modern CSS - This allows us to still use tables (for tabular data - maybe from anohter source), and still be responsive Great video!

Rico and Vettle real GOATs.

Holy timely, Batman! I just started looking into this yesterday.

Nice and simple explanation! Looks like a jump cut edited out the formatting of the before container width at the 20:56 mark. Things went from in-line to column formatting.

I've been struggling with CSS and every video you made has clarified every issue i have with. Now i can make decent web sites that doesn't look as they were made for Netscape

I like it that you choose F1. It made the video a lot more interesting 😊

your highness sir!❤

Superb, you are really master.

Amazing! Thanks!

as always its fantastic!! :)

Absolutely god tier video

This video has levelled up my approach to tables responsiveness. Thank you so much, Kevin!

Narrower viewports usually (though not always) are on mobile, which has a touch interface, and so the scrollbar at the bottom is less of an issue. Also, the thead and tbody would be good to add (browsers will probably add it in anyways, but it's better to specify it yourself so you can better troubleshoot things). For example the table headers (first row) got lumped into the tbody

@Ekitchi0

Жыл бұрын

Also with mouse and keyboard Shift+mouse scroll scrolls horizontally

@Warface

Жыл бұрын

Exactly

@mina86

Жыл бұрын

FYI, in HTML5 browser adds TBODY automatically. Neither THEAD nor TFOOT is added automatically. In HTML4 and older nothing is added (so TR is direct child of TABLE).

I had the trouble of working with tables and found a nice solution. Switching were possible from rows to columns, and placing the thread rows at first

Very nice!

We're not using thead? I was wondering if that was part of accessibility or just declarative if your header has multiple rows?

Pretty neat skill to have. You will have to work with tables at some point in your FE job if you're working for companies. Also worth to learn about how to make the sticky thead or footer when scrolling. Just another tutorial idea 😁

Before my recent retirement, my team supported a LOT of HR-data related intranet sites where the output was tabular. We used the data-attribute method and it worked quite well. One thing with the display-grid method (which we did not use) is that it handles even narrower layouts since a single header/data element combo take up a single column, which would reduce the overflow seen around 23:55.

The complete and proper nesting would be table caption colgroup thead (max 1) tfoot (max 1) tbody (1-n times) Yes *tfoot* comes before any tbody groups. The browser will still render it at the bottom. This is to support paged media rendering where the footer is repeated on every page

This is great, cause I am just about to create table in NextJs app that I am actually working on in my youtube channel so thanks a lot Kevin 👍

wow... very practical tips

Another great video.

Awesome ♥♥♥

Interesting indeed. I'd have put in thead and tbody as others have mentioned but overall it is tidy. Couple of styling bits you did that I'm going to implement just to save space but also give general breathing room 🙂 I've hated tables for years but they do have their uses. I think they're the only thing I generally come across that is "desktop first" design. Still a pain though 😂

Rico "Bobby" Rosberg was undeniable, quite "suave". Definitely my favorite champion!

Great video Kevin!

Love or hate them, tables have their place in web design. I started designing sites with tables and this was before css files existed, all styles were tagged with each element. Fun times. Back then one didn't have to worry about responsiveness so it was easy to churn websites out at a high rate.

As a brazilian, thank you for adding Senna!

I've been using the tailwind table utility classes and tanstack-table for implementing tables and data-grids 😅... Also a big F1 fan!!!

Love the shout out to Adrian Roselli, he does amazing work on accessibility! On that note, I'm afraid the scrolling solution needs a little more to work properly, as Adrian also points out in "Under-engineered responsive tables". 1. It needs to be focusable otherwise you can't scroll by keyboard. Firefox does this automatically but other browsers do not. 2. It needs an accessible name so screen readers can tell the user what it is that has taken focus. 3. It needs a role so that the accessible name will be accepted.

I love the way that your brain works.

Someone else mentioned that data attributes are great for dealing with multiple languages, which I 100% agree with, Another good reason for that approach, vs the css version is if you have merged cells. The css version will mess things up vs the data-attribute version which won't.

I remember doing this for a client 10 years ago, data attributes where not a thing, but :before and after were starting to be used, it was not as clean as this but content did the work.

Very helpfull. love you Videos.

Thanks a lot!

I know this is an HTML table tutorial, but I certainly love the F1 aspect, and historically "Our Nige" is my favorite driver too!

Finally. This IS not a video, THIS IS THE VIDEO!

Great Kevin!!!

great turorial

Didn't know the semantic could break with CSS. I mean, of course I knew that a display : none would eventually prevent screen readers to describe an element, but I was not aware that a display block on a table,tr,td,... element would change its semantic. Thanks a lot !

Very helpful, thank you! Could you further use the media query to have the right side of each row on mobile have an 'id' block which takes up the full height of the row?

Omg, I’d almost managed to forget the days of table layout and single pixel transparent gifs everywhere

Hi Kevin, thanks for the awesome video. I wish the tables that I have to build for educational products didn't have to be accessible.

Many thanks

Wow, i didn't know you are into F1. That's great.

You forgot the GOAT - Latifi. I actually had a tough time tackling a responsive table about a month ago. And, sometime you just gotta use a table. I just implemented this solution. Thank you for doing this video. Also, I think Fernando changed his name to Alonstroll.