diff --git a/src/pages/404.astro b/src/pages/404.astro
index 0ebca24..6a4dc26 100644
--- a/src/pages/404.astro
+++ b/src/pages/404.astro
@@ -64,14 +64,6 @@ const description = 'The page you requested does not exist.';
     background-color: var(--paper);
   }
 
-  /* Same as index: no scroll on desktop, so the bounce only exists to expose
-     chrome-side fills the page cannot colour. */
-  @media (min-width: 721px) {
-    html {
-      overscroll-behavior: none;
-    }
-  }
-
   body {
     margin: 0;
     min-width: 320px;
diff --git a/src/pages/index.astro b/src/pages/index.astro
index f621ae0..28c2ed4 100644
--- a/src/pages/index.astro
+++ b/src/pages/index.astro
@@ -159,18 +159,13 @@ const canonical = new URL('/', Astro.site);
     background-color: var(--paper);
   }
 
-  /* Desktop only: the page fits the viewport there, so the rubber band is pure
-     decoration — and macOS Safari fills parts of that bounce from chrome-side
-     surfaces the page cannot colour (the render-time tint sample, the refresh
-     spinner well), which is where the band still leaked through after every
-     page-side colour was right. No bounce, no surface to mis-fill. Phones keep
-     the native feel: the page actually scrolls there, iOS honours body's
-     background-color for the gap, and none would also cost pull-to-refresh. */
-  @media (min-width: 721px) {
-    html {
-      overscroll-behavior: none;
-    }
-  }
+  /* The rubber band is deliberately allowed everywhere, desktop included. It was
+     suppressed on wide viewports for a while (overscroll-behavior: none) when the
+     bounce was exposing fills the page didn't yet control — but the owner found the
+     page felt dead without it, and by now every pixel a bounce can reveal is owned:
+     body's background-color fills the gap, and the ambient layer carries its own
+     --paper apron beyond every edge. If banding ever returns out there, fix the
+     surface it comes from rather than re-locking the scroll. */
 
   body {
     margin: 0;