From 9ba62f0f124d6ffd7d6bede838f8d70c2a3e85da Mon Sep 17 00:00:00 2001
From: saberzero1 <github@emilebangma.com>
Date: Fri, 13 Feb 2026 20:47:51 +0100
Subject: [PATCH] fix: remove imperative navigation in folder link handler to
 fix SPA routing

When folderBehavior is 'link', the buttonClickHandler was using
window.location.href with a relative URL (e.g. 'features/'), which
resolved against the current path and broke navigation between folder
pages. Now the handler simply returns, letting the <a> tag's correct
absolute href propagate to the SPA router.
---
 src/components/scripts/explorer.inline.ts | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/components/scripts/explorer.inline.ts b/src/components/scripts/explorer.inline.ts
index f78aa82..0127d1e 100644
--- a/src/components/scripts/explorer.inline.ts
+++ b/src/components/scripts/explorer.inline.ts
@@ -356,10 +356,10 @@ document.addEventListener("nav", async (e) => {
           const folderPath = folderContainer.dataset.folderpath;
 
           if (folderBehavior === "link") {
-            if (folderPath) {
-              const folderHref = simplifySlug(folderPath);
-              window.location.href = folderHref || ".";
-            }
+            // When folderBehavior is "link", the <button> has been replaced with an <a> tag
+            // that has the correct absolute href (e.g. "/features/"). Let the <a> tag's
+            // native click propagate to the SPA router — don't navigate imperatively here,
+            // as that would use a relative URL and break SPA navigation.
             return;
           } else {
             evt.stopPropagation();