diff options
| author | bt <bt@web> | 2023-12-09 09:52:39 -0500 |
|---|---|---|
| committer | IkiWiki <ikiwiki.info> | 2023-12-09 09:52:39 -0500 |
| commit | 9780cc4857eb88a91dedcdc6beead11875483eab (patch) | |
| tree | 8963f778027214ba1c3a395502ef896d3a7f3050 | |
| parent | a6168107159b0523193536aab9aff169a26a8889 (diff) | |
| -rw-r--r-- | posts/obvious-js-injection-fallback.md | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/posts/obvious-js-injection-fallback.md b/posts/obvious-js-injection-fallback.md index 5143f7f..1d93367 100644 --- a/posts/obvious-js-injection-fallback.md +++ b/posts/obvious-js-injection-fallback.md @@ -1,6 +1,5 @@ -# Obvious Javascript 'Injection' Fallback - -2020-12-04 +[[!meta title="Obvious Javascript 'Injection' Fallback"]] +[[!meta date="2020-12-04"]] 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 *empty* HTML elements with the assumption they will be filled via Javascript. |