From 7b49b4aac6b89b4cc8bc7dbc505c99b3efa4fff5 Mon Sep 17 00:00:00 2001 From: Harry Roberts Date: Wed, 14 Aug 2024 15:55:46 +0100 Subject: [PATCH] Add footnote/credit --- _posts/2024-08-14-blocking-render-why-whould-you-do-that.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/_posts/2024-08-14-blocking-render-why-whould-you-do-that.md b/_posts/2024-08-14-blocking-render-why-whould-you-do-that.md index a225334b..550c90f0 100644 --- a/_posts/2024-08-14-blocking-render-why-whould-you-do-that.md +++ b/_posts/2024-08-14-blocking-render-why-whould-you-do-that.md @@ -168,7 +168,7 @@ want to maybe use `blocking=render`. But even then, I wouldn’t. web-font `preload`s already. It’s non-standard behaviour, but Chrome [will make font preloads block rendering until they finish or until a timeout](https://chromestatus.com/feature/5087982807154688). This is -already happening and you don’t need `blocking=render`. +already happening and you don’t need `blocking=render`.[^1] ## A/B Testing and Experimentation @@ -268,3 +268,7 @@ following: …to behave like this: * `` + +- - - + +[^1]: [x.com/kurtextrem/status/1823698340388782591](https://x.com/kurtextrem/status/1823698340388782591)