aboutsummaryrefslogtreecommitdiff
path: root/build/tabbed-content/index.html
diff options
context:
space:
mode:
authorBradley Taunt <bt@btxx.org>2024-06-06 08:05:12 -0400
committerBradley Taunt <bt@btxx.org>2024-06-06 08:05:12 -0400
commit6b742c459266b18e2b375b35205ce8a6c02f0452 (patch)
treeb16fbb9a045e33dd6c97eb5ab72e6ff4d9237ea3 /build/tabbed-content/index.html
Initial commit
Diffstat (limited to 'build/tabbed-content/index.html')
-rw-r--r--build/tabbed-content/index.html250
1 files changed, 250 insertions, 0 deletions
diff --git a/build/tabbed-content/index.html b/build/tabbed-content/index.html
new file mode 100644
index 0000000..295a712
--- /dev/null
+++ b/build/tabbed-content/index.html
@@ -0,0 +1,250 @@
+<!doctype html>
+<html lang="en" id="top">
+<head>
+ <meta charset="utf-8">
+ <meta name="viewport" content="width=device-width, initial-scale=1">
+ <link rel="icon" href="data:,">
+ <title>Tabbed Content Without JavaScript</title>
+ <link href="https://bt.ht/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" />
+ <style>*{box-sizing:border-box;}body{font-family:sans-serif;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{overflow:auto;}table{text-align:left;width:100%;}</style>
+</head>
+
+<nav>
+ <a href="#menu">Menu &darr;</a>
+</nav>
+
+<main>
+<h1>Tabbed Content Without JavaScript</h1>
+<p>2019-01-28</p>
+<p>Creating tabs is a fairly trivial and common practice in web design, but many times it requires JavaScript to properly implement. Fortunately it <em>is</em> possible to create tabbed content with only using CSS.</p>
+<p><img src="/public/images/tabbed-content.png" alt="Tabbed elements with only CSS" /></p>
+<p><a href="https://codepen.io/bradleytaunt/pen/abjmayw">Live CodePen Example</a></p>
+<hr />
+<p><div class="message">
+<p><strong>Sidenote:</strong></p>
+<p>While this method is semantic and accessible, you might consider using a pre-existing plugin for tabbed data.</p>
+<p>This component tends to feel a little "stiff" compared to more fleshed out variations available. This pure CSS version is better suited as a fallback for when users have disabled JavaScript.</p>
+</div></p>
+<h2>The HTML</h2>
+<p>The skeleton for this component is fairly basic - we just need the following structure:</p>
+<ol>
+<li>Parent element for each tab item</li>
+<li>Default radio input</li>
+<li>Label linked to corresponding input</li>
+<li>Inner content associated with each tab item</li>
+</ol>
+<pre><code>&lt;!-- Simple main container for all elements --&gt;
+&lt;div class=&quot;tabs&quot;&gt;
+
+ &lt;!-- Parent container holding for individual tab item --&gt;
+ &lt;div class=&quot;tab-item&quot;&gt;
+
+ &lt;!-- Default radio input --&gt;
+ &lt;input class=&quot;tab-input&quot; type=&quot;radio&quot; name=&quot;tabs&quot; id=&quot;tab-1&quot;&gt;
+
+ &lt;!-- Label connected to radio input via `id` and `for` attributes --&gt;
+ &lt;label class=&quot;tab-label&quot; for=&quot;tab-1&quot;&gt;Tab 1&lt;/label&gt;
+
+ &lt;!-- Full inner content of current tab item --&gt;
+ &lt;div class=&quot;tab-content&quot;&gt;Content goes here&lt;/div&gt;
+
+ &lt;/div&gt;
+
+&lt;/div&gt;
+</code></pre>
+<p>Full HTML for reference:</p>
+<pre><code>&lt;div class=&quot;tabs&quot;&gt;
+
+ &lt;div class=&quot;tab-item&quot;&gt;
+ &lt;input class=&quot;tab-input&quot; type=&quot;radio&quot; name=&quot;tabs&quot; id=&quot;tab-1&quot;&gt;
+ &lt;label class=&quot;tab-label&quot; for=&quot;tab-1&quot;&gt;Tab 1&lt;/label&gt;
+ &lt;div class=&quot;tab-content&quot;&gt;Content goes here&lt;/div&gt;
+ &lt;/div&gt;
+
+ &lt;div class=&quot;tab-item&quot;&gt;
+ &lt;input class=&quot;tab-input&quot; type=&quot;radio&quot; name=&quot;tabs&quot; id=&quot;tab-2&quot;&gt;
+ &lt;label class=&quot;tab-label&quot; for=&quot;tab-2&quot;&gt;Tab 2&lt;/label&gt;
+ &lt;div class=&quot;tab-content&quot;&gt;Content goes here&lt;/div&gt;
+ &lt;/div&gt;
+
+ &lt;div class=&quot;tab-item&quot;&gt;
+ &lt;input class=&quot;tab-input&quot; type=&quot;radio&quot; name=&quot;tabs&quot; id=&quot;tab-3&quot;&gt;
+ &lt;label class=&quot;tab-label&quot; for=&quot;tab-3&quot;&gt;Tab 3&lt;/label&gt;
+ &lt;div class=&quot;tab-content&quot;&gt;Content goes here&lt;/div&gt;
+ &lt;/div&gt;
+
+&lt;/div&gt;
+</code></pre>
+<h2>The CSS</h2>
+<p>First, we need to set each <code>input</code>, <code>label</code> and inner content into their own parent containers:</p>
+<pre><code>/* Main parent that holds all contents */
+.tabs {
+ height: 100%;
+ min-height: 250px;
+ position: relative;
+}
+
+/* Each tab items (includes heading &amp; content) */
+.tab-item {
+ display: inline;
+}
+</code></pre>
+<p>Next, we will hide the default <code>radio</code> input and design our labels to resemble a basic web tab element. The <code>z-index</code> property on the label is important for how we will be stacking our content on the z-axis (labels above inner content for example).</p>
+<pre><code>/* Hide the default radio inputs */
+.tab-input {
+ position: absolute;
+ visibility: hidden;
+}
+
+/* The main tab headings */
+.tab-label {
+ background: white;
+ box-shadow: inset 0 -4px 4px rgba(0,0,0,0.02);
+ color: lightgrey;
+ cursor: pointer;
+ display: inline-block;
+ font-weight: 600;
+ margin: 0 5px 0 0;
+ padding: 10px 20px;
+ position: relative;
+ text-align: center;
+ z-index: 0;
+}
+</code></pre>
+<p>The main inner content of each tab needs to have an <code>absolute</code> position set as it's default, since the one currently selected will switch to <code>relative</code> on mobile (more on that in a moment):</p>
+<pre><code>/* The inner tab content */
+.tab-content {
+ background: white;
+ bottom: 0;
+ box-shadow: 0 6px 8px rgba(0,0,0,0.02);
+ left: 0;
+ overflow: scroll;
+ padding: 20px;
+ position: absolute;
+ right: 0;
+ top: 50px;
+ z-index: 0;
+}
+</code></pre>
+<p>The final step is just telling the browser to style both the <code>label</code> and inner content of the currently selected radio <code>input</code>:</p>
+<pre><code>/* Style the currently selected tab label */
+.tab-input:checked + .tab-label {
+ border: 1px solid #eee;
+ border-bottom: 0;
+ box-shadow: 0 -6px 8px rgba(0,0,0,0.02);
+ color: #268bd2;
+ z-index: 2;
+}
+
+/* Show the currently selected tab content */
+.tab-input:checked ~ .tab-content {
+ border: 1px solid #eee;
+ z-index: 1;
+}
+</code></pre>
+<p>It's as simple as that! For reference, here is the entire CSS file for easier access:</p>
+<pre><code>/* Main parent that holds all contents */
+.tabs {
+ height: 100%;
+ min-height: 250px;
+ position: relative;
+}
+
+/* Each tab items (includes heading &amp; content) */
+.tab-item {
+ display: inline;
+}
+
+/* Hide the default radio inputs */
+.tab-input {
+ position: absolute;
+ visibility: hidden;
+}
+
+/* The main tab headings */
+.tab-label {
+ background: white;
+ box-shadow: inset 0 -4px 4px rgba(0,0,0,0.02);
+ color: lightgrey;
+ cursor: pointer;
+ display: inline-block;
+ font-weight: 600;
+ margin: 0 5px 0 0;
+ padding: 10px 20px;
+ position: relative;
+ text-align: center;
+ z-index: 0;
+}
+
+/* The inner tab content */
+.tab-content {
+ background: white;
+ bottom: 0;
+ box-shadow: 0 6px 8px rgba(0,0,0,0.02);
+ left: 0;
+ overflow: scroll;
+ padding: 20px;
+ position: absolute;
+ right: 0;
+ top: 50px;
+ z-index: 0;
+}
+
+/* Style the currently selected tab label */
+.tab-input:checked + .tab-label {
+ border: 1px solid #eee;
+ border-bottom: 0;
+ box-shadow: 0 -6px 8px rgba(0,0,0,0.02);
+ color: #268bd2;
+ z-index: 2;
+}
+
+/* Show the currently selected tab content */
+.tab-input:checked ~ .tab-content {
+ border: 1px solid #eee;
+ z-index: 1;
+}
+</code></pre>
+<h2>Don't forget about mobile</h2>
+<p>With only a few extra lines of CSS we can ensure that our custom tabs will stack on top of each other and look solid on mobile devices:</p>
+<pre><code>@media(max-width:38em) {
+ .tab-label {
+ display: block;
+ width: 100%;
+ }
+ .tab-content {
+ display: none;
+ }
+ .tab-input:checked ~ .tab-content {
+ bottom: auto;
+ display: block;
+ position: relative;
+ top: auto;
+ }
+}
+</code></pre>
+<h2>One minor caveat</h2>
+<p>Even though I'm a pretty big fan of implementing tabs this way, there is a small drawback:</p>
+<p>The <code>height</code> of the inner content doesn't grow dynamically since it defaults as <code>absolute</code>, so a <code>min-height</code> or <code>height</code> value is required on the parent element. This could become a problem in certain situations where you don't have the luxury of setting a static height.</p>
+<p>Other than that, enjoy building some JavaScript-free tabs!</p>
+<footer role="contentinfo">
+ <h2>Menu Navigation</h2>
+ <ul id="menu">
+ <li><a href="/">Home</a></li>
+ <li><a href="/projects">Projects</a></li>
+ <li><a href="/uses">Uses</a></li>
+ <li><a href="/wiki">Wiki</a></li>
+ <li><a href="/resume">Resume</a></li>
+ <li><a href="/colophon">Colophon</a></li>
+ <li><a href="/now">Now</a></li>
+ <li><a href="/donate">Donate</a></li>
+ <li><a href="/atom.xml">RSS</a></li>
+ <li><a href="#top">&uarr; Top of the page</a></li>
+ </ul>
+ <small>
+ Built with <a href="https://git.sr.ht/~bt/barf">barf</a>. <br>
+ Maintained with ♥ for the web. <br>
+ Proud supporter of <a href="https://usefathom.com/ref/DKHJVX">Fathom</a> &amp; <a href="https://nextdns.io/?from=74d3p3h8">NextDNS</a>. <br>
+ The content for this site is <a href="https://creativecommons.org/licenses/by-sa/2.0/">CC-BY-SA</a>.<br> The <a href="https://git.sr.ht/~bt/bt.ht">code for this site</a> is <a href="https://git.sr.ht/~bt/bt.ht/tree/master/item/LICENSE">MIT</a>.
+ </small>
+</footer> \ No newline at end of file