aboutsummaryrefslogtreecommitdiff
path: root/build/posts/jsincss-parent-selector/index.html
diff options
context:
space:
mode:
authorBradley Taunt <bt@btxx.org>2024-06-10 09:41:25 -0400
committerBradley Taunt <bt@btxx.org>2024-06-10 09:41:25 -0400
commit07e4a2dafe248280b5610f8c7d09b0f30b530f54 (patch)
tree8a145d1d4d07e1278a837ff15dadccc322d27515 /build/posts/jsincss-parent-selector/index.html
parent16d28628aca9b2d356de31c319f5e7bc0f5b2b02 (diff)
Initial modifications to rebuilt only changed files based on mod date, performance updates
Diffstat (limited to 'build/posts/jsincss-parent-selector/index.html')
-rw-r--r--build/posts/jsincss-parent-selector/index.html94
1 files changed, 94 insertions, 0 deletions
diff --git a/build/posts/jsincss-parent-selector/index.html b/build/posts/jsincss-parent-selector/index.html
new file mode 100644
index 0000000..a4ad5cc
--- /dev/null
+++ b/build/posts/jsincss-parent-selector/index.html
@@ -0,0 +1,94 @@
+<!doctype html>
+<html lang="en">
+<head>
+ <meta charset="utf-8">
+ <meta name="viewport" content="width=device-width, initial-scale=1">
+ <meta name="color-scheme" content="dark light">
+ <link rel="icon" href="data:,">
+ <title>Using Parent Selectors in CSS</title>
+ <link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" />
+ <link href="/rss.xml" type="application/rss+xml" rel="alternate" title="RSS feed for blog posts" />
+<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}blockquote{background:rgba(0,0,0,0.1);border-left:4px solid;padding-left:5px;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style>
+</head>
+
+<nav>
+ <a href="#menu">Menu &darr;</a>
+</nav>
+
+<main>
+<h1 id="using-parent-selectors-in-css">Using Parent Selectors in CSS</h1>
+<p>2018-12-19</p>
+<p>I recently saw a Twitter thread posted by Tommy Hodgins on implementing highly requested styling features in CSS with only a minimal amount of JavaScript. Many of his examples are great, but the <code>parent</code> selector instantly peaked my interest.</p>
+<p>Being able to target an element&#8217;s parent always becomes a minor annoyance (since vanilla CSS does not support it) - so you always end up having to do something a little ugly like:</p>
+<pre><code>var el = document.getElementById(&#39;custom-div&#39;);
+var parent = el.closest(selectors);
+</code></pre>
+<p>And then add any custom styling to the parent element directly in JavaScript - or toggle a class which opens a whole other can of worms.</p>
+<h2 id="save-the-day-with-jsincss-parent-selector-and-qaffeine">Save the day with jsincss-parent-selector and qaffeine</h2>
+<p>By using the <code>jsincss-parent-selector</code> and <code>qaffeine</code> plugins we can target an element&#8217;s parent in CSS without breaking a sweat. Let&#8217;s break it down:</p>
+<h3 id="import-the-packages">Import the packages</h3>
+<pre><code>npm install jsincss-parent-selector qaffeine
+</code></pre>
+<h3 id="html-ex.-index.html">HTML (ex. index.html)</h3>
+<p>Now we add our very simple HTML skeleton:</p>
+<pre><code>&#60;!doctype html&#62;
+&#60;html&#62;
+ &#60;head&#62;
+ &#60;link rel="stylesheet" href="output.css"&#62;
+ &#60;&#47;head&#62;
+ &#60;body&#62;
+ &#60;header&#62;
+ &#60;main&#62;
+ &#60;h2&#62;This is a header&#60;&#47;h2&#62;
+ &#60;&#47;main&#62;
+ &#60;&#47;header&#62;
+ &#60;&#47;body&#62;
+ &#60;script src=output.js&#62;&#60;&#47;script&#62;
+&#60;&#47;html&#62;
+</code></pre>
+<h3 id="javascript-ex.-input.js">JavaScript (ex. input.js)</h3>
+<pre><code>const qaffeine = require(&#39;qaffeine&#39;)
+const parent = require(&#39;jsincss-parent-selector&#39;)
+
+qaffeine(
+{
+ stylesheet: {},
+ rules: {
+ parent
+ }
+},
+&#39;input.css&#39;,
+&#39;output.js&#39;,
+&#39;output.css&#39;
+)
+</code></pre>
+<h3 id="css-ex.-input.css">CSS (ex. input.css)</h3>
+<pre><code>header {
+ display: block;
+}
+main[--js-parent] {
+ background: blue;
+}
+</code></pre>
+<p>Then simply run <code>node</code> against your <code>js</code> file. That&#8217;s it! I would also suggest checking out Tommy&#8217;s video covering this topic if you prefer to follow along.</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