tosijs-ui 1.16.5 → 1.16.6

package/CHANGELOG.md

@@ -1,5 +1,25 @@
 # Changelog
 
+## 1.16.6
+
+A one-fix patch: a link to the page you are already on no longer adds a history entry that Back
+has to step through (#174). No API change.
+
+### Clicking a link to the page you are on no longer costs an extra Back (#174)
+
+A doc link pointing at the document already showing pushed a duplicate history entry, so the
+next Back press left the page where it was. It now replaces the entry, as a native same-URL
+navigation does. "The same page" means the same document: `/x`, `/x/` and `/x/index.html`, or
+`?x` with extra query parameters, all count. A URL with a hash still pushes, so Back from
+`/x/` returns to `/x/#example`. The `router`'s `navigate()` had the same defect and gets the
+same rule: navigating to the current path (with no hash) replaces.
+
+The double push #174 measured on every link (ensemble on 1.14.1) does not reproduce on 1.16.4
+with the same direct import: one click, one entry, and Back and Forward both work, in Chromium
+and WebKit. The documented consumer entry point is `import 'tosijs-ui/doc-browser'`, which
+registers `<tosi-doc-system>` since 1.14.2. The deep `tosijs-ui/doc-system/doc-system.js`
+import loads the same module.
+
 ## 1.16.5
 
 A patch, mostly found by using the doc site on an iPhone: menus that stay on screen as Safari's

package/dist/doc-browser.js

@@ -1027,7 +1027,19 @@ export function createDocBrowser(options) {
         }
         else {
             const href = hrefFor(filename);
-            window.history.pushState({ href }, '', href);
+            /*
+            A link to the document already showing REPLACES the entry rather than pushing one, as a
+            native same-URL navigation does. Pushing left a duplicate the reader had to Back
+            through, and Back then visibly did nothing — the symptom #174 reported.
+      
+            "Same" is the DOCUMENT, the identity the popstate guard uses, not the raw path: `/x`,
+            `/x/` and `/x/index.html`, or `?x` and `?x&_testMode=1`, are one page. A URL carrying a
+            hash still pushes, because leaving `/x/#example` for `/x/` is a navigation the reader
+            may want to come Back from.
+            */
+            const same = filename === String(app.currentDoc.filename) &&
+                document.location.hash === '';
+            window.history[same ? 'replaceState' : 'pushState']({ href }, '', href);
         }
         navigateTo(filename);
     };