diff options
Diffstat (limited to 'build/obvious-js-injection-fallback')
| -rw-r--r-- | build/obvious-js-injection-fallback/index.html | 21 |
1 files changed, 2 insertions, 19 deletions
diff --git a/build/obvious-js-injection-fallback/index.html b/build/obvious-js-injection-fallback/index.html index e1e2880..813f76a 100644 --- a/build/obvious-js-injection-fallback/index.html +++ b/build/obvious-js-injection-fallback/index.html @@ -3,11 +3,12 @@ <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>Obvious Javascript 'Injection' Fallback</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;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style> +<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> @@ -16,49 +17,31 @@ <main> <h1 id="obvious-javascript-injection-fallback">Obvious Javascript ‘Injection’ Fallback</h1> - <p>2020-12-04</p> - <p>Sometimes websites and web apps might require content to be “injected” via Javascript. I should mention that I am strongly against this practice - but often this kind of thing is out of one’s hands. So, the least I can do is setup these “injections” to have proper fallbacks for users who disable JS. You would be surprised how many developers build <em>empty</em> HTML elements with the assumption they will be filled via Javascript.</p> - <h2 id="our-hypothetical-project">Our Hypothetical Project</h2> - <p>Let’s pretend that we have a total tally that pulls in the number of current users using our fake SaaS app. We would do something like this:</p> - <h3 id="html">HTML</h3> - <p>Here we create an empty <code>h2</code> tag that will update with the current number of users via js:</p> - <pre><code><main> <h2 class="total-tally"></h2> </main> </code></pre> - <h3 id="javascript">Javascript</h3> - <p>You’ll have to use your imagination here and assume that the <code>totalTally</code> variable pulls in the numbers dynamically via API:</p> - <pre><code>var totalTally = "273,677" /* This would pull something dynamically in prod */ document.getElementsByClassName("total-tally")[0].innerHTML=totalTally; </code></pre> - <h2 id="the-problem">The Problem</h2> - <p>The big issue we have now occurs when a user visits this page without JS enabled. The <code>h2</code> tag will remain empty and they won’t see anything. I know this seems like a very avoidable issue, but you would be surprised how often it actually happens on the web.</p> - <h2 id="the-overly-simple-solution">The (overly simple) Solution</h2> - <p>The easiest way to avoid these types of empty tags - add static content. I know - mind blowing, right?</p> - <h3 id="html-updated">HTML (updated)</h3> - <pre><code><main> <h2 class="total-tally">200,000+</h2> </main> </code></pre> - <p>You might be reading this and saying to yourself, “Wow! Thanks Captain Obvious!” and that’s a fair reaction. This is an <em>obvious</em> demo on purpose. If even one single reader learns to avoid leaving empty HTML tags that are solely dependent on Javascript injection, then I’d say this demo was a huge success.</p> - <p>Rule of thumb: don’t make assumption about your users. Play it safe.</p> <footer role="contentinfo"> <h2>Menu Navigation</h2> |