Skip to content

Commit

Permalink
Add anti-flicker screenshot
Browse files Browse the repository at this point in the history
  • Loading branch information
csswizardry committed Aug 14, 2024
1 parent 44839f6 commit 2380d0a
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions _posts/2024-08-14-blocking-render-why-whould-you-do-that.md
Original file line number Diff line number Diff line change
Expand Up @@ -234,6 +234,12 @@ and good user experience—but a user didn’t benefit from it. Anti-flicker
snippets eschew this behaviour and take an all-or-nothing approach: nothing,
nothing, nothing, _everything_.

<figure>
<img src="{{ site.cloudinary }}/wp-content/uploads/2024/08/anti-flicker.png" alt="" width="750" height="223">
<figcaption>A regular, progressive render (top) versus an anti-flicker
big-reveal (bottom). Which do you think is the better experience?</figcaption>
</figure>

`blocking=render` leaves the browser to its usual rendering process, so we can
still get a progressive render of the page, only now we do it in a way more
akin to loading a CSS file.
Expand Down

0 comments on commit 2380d0a

Please sign in to comment.