From 305ee81a10cd119625f3abb391ce0ea89d6dcfa4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Lauren=C8=9Biu=20Nicola?= Date: Sat, 29 Aug 2026 20:47:30 +0300 Subject: [PATCH] Fix typo in 4.0 announcement --- .../content/announcements/2026-08-28-htmx-4.0.0-is-released.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/www/src/content/announcements/2026-08-28-htmx-4.0.0-is-released.md b/www/src/content/announcements/2026-08-28-htmx-4.0.0-is-released.md index 2306a7624..b3ba92373 100644 --- a/www/src/content/announcements/2026-08-28-htmx-4.0.0-is-released.md +++ b/www/src/content/announcements/2026-08-28-htmx-4.0.0-is-released.md @@ -101,7 +101,7 @@ them. History support has always been included in htmx, allowing you to implement back-button aware actions with simple attributes. In htmx 2, a cache in `localStorage` was used to snapshot pages for restoration. Unfortunately a large source of issues was that this snapshot could include DOM mutations by 3rd party JavaScript libraries. When the page was -restored, those mutations remained by the underlying JavaScript logic was not. +restored, those mutations remained by the underlying JavaScript logic did not. htmx 4 does not cache pages in `localStorage`. On back navigation htmx re-fetches the page and swaps it into ``, or into the `[hx-history-elt]` element if one is present. This allows 3rd party JavaScript libraries to "just work" in