aboutsummaryrefslogtreecommitdiff
path: root/posts/Please_Make_Your_Table_Headings_Sticky.md
diff options
context:
space:
mode:
Diffstat (limited to 'posts/Please_Make_Your_Table_Headings_Sticky.md')
-rw-r--r--posts/Please_Make_Your_Table_Headings_Sticky.md16
1 files changed, 14 insertions, 2 deletions
diff --git a/posts/Please_Make_Your_Table_Headings_Sticky.md b/posts/Please_Make_Your_Table_Headings_Sticky.md
index b64928d..ef2e810 100644
--- a/posts/Please_Make_Your_Table_Headings_Sticky.md
+++ b/posts/Please_Make_Your_Table_Headings_Sticky.md
@@ -4,7 +4,14 @@
I often stumble upon large data sets or table layouts across the web. When these tables contain hundreds of rows of content, things become problematic once you start to scroll...
-[Link to video example of standard table header](/public/videos/not-fixed-header-tables.mp4)
+
+<video width="100%" controls>
+<source src="https://btxx.org/posts/Please_Make_Your_Table_Headings_Sticky/not-fixed-header-tables.mp4" type="video/mp4">
+Your browser does not support the video tag.
+</video>
+
+
+<h2>This should be a header</h2>
Look at that table header disappear! Now, if I scroll all the way down to item #300 (for example) will I remember what each column's data is associated with? If this is my first time looking at this table - probably not. Luckily we can fix this (no pun intended!) with a tiny amount of CSS.
@@ -12,7 +19,12 @@ Look at that table header disappear! Now, if I scroll all the way down to item #
Check it out:
-[Link to video example of fixed table header](/public/videos/fixed-header-tables.mp4)
+
+<video width="100%" controls>
+<source src="https://btxx.org/ikiwiki/git/fixed-header-tables.mp4" type="video/mp4">
+Your browser does not support the video tag.
+</video>
+
Pretty awesome, right? It might look like magic but it's actually very easy to implement. You only need to add 2 CSS properties on your `thead`: