summaryrefslogtreecommitdiff
path: root/posts/obvious-js-injection-fallback.md
diff options
context:
space:
mode:
Diffstat (limited to 'posts/obvious-js-injection-fallback.md')
-rw-r--r--posts/obvious-js-injection-fallback.md5
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.