@jsenv/navi 0.29.457 → 0.29.459

package/docs/dynamic_import.md

@@ -145,6 +145,24 @@ that asks for nothing (`() => true`).
 `routeAction(route, action, undefined, { prefetch: false })` keeps a param-less
 read that is not worth a hover out of it.
 
+A page only some readers may download keeps its condition out of the params and
+says it with `when`: a condition on app state, not on the address, so the link
+still prefetches the action, as long as the condition holds when the pointer
+arrives. A reader for whom it does not hold downloads nothing, not even by
+typing the address.
+
+```js
+const VIDEO_PAGE_CODE = routeAction(
+  VIDEO_ROUTE,
+  () => import("./video_page.jsx").then((m) => m.VideoPage),
+  undefined,
+  { when: () => meIsAdminSignal.value },
+);
+```
+
+The link reads `when` as it is at that moment, not as the address it leads to
+will make it: a condition that reads the address belongs in the params.
+
 A prefetch that fails is not reported: nothing on screen asked for it. The failure
 stays on the action, and a failed action is run again by whatever asks next — the
 arrival, which shows its own failure, and every later hover alike.

package/docs/navigation.md

@@ -784,8 +784,10 @@ Every piece of it answers something:
   off screen;
 - **no `defineRouteTransition` for it.** The page beneath does not change, so
   there is no pair of pages to move between — route transitions are for pages
-  replacing pages ([route_transitions.md](./route_transitions.md)). When a link
-  inside the layer does change it, see
+  replacing pages ([route_transitions.md](./route_transitions.md)). Nor does
+  what is open on it: a popup or a section kept with `navState` stays open under
+  the layer ([popup_open.md](./popup_open.md#navstate--the-history-entry-holds-it)).
+  When a link inside the layer does change the page, see
   [below](#a-link-inside-the-layer-leads-to-a-page).
 
 ### Places inside the layer

package/docs/popup_open.md

@@ -680,6 +680,23 @@ picker open and come back to is a new mount, and the state stays in the entry
 with nothing to read it (navi warns). A picker whose popup leads somewhere, a
 link inside it, has an `id`.
 
+What a new entry inherits is decided by the page, not by the address. A push to
+another path starts its entry empty: a popup open on the page being left
+describes that page alone, and carried onto the next one it would open whatever
+mounts there under the same key. A push that keeps the path — a
+[layer](./navigation.md#a-layer-over-the-screen-what-its-address-may-say)
+opening over the page, a
+[state whose values are places](./navigation.md#a-state-whose-values-are-places-history-push)
+— stacks an entry over a page that is still mounted, and that entry starts with
+what the one below it held: an `Expandable` section open under the layer stays
+open, and closing the layer finds it as it was, with nothing played again. The
+scroll reads the same rule
+([navigation.md](./navigation.md#where-a-navigation-lands-the-scroll)).
+
+A link inside the popup follows the same rule: one to the same path with other
+search params leaves the popup open on the entry it pushes. A link whose press
+is a choice that ends the popup says so itself, with `command="--navi-close"`.
+
 The two meet when the signal IS a route's: a search-param `stateSignal` given to
 `signal` puts the open state in the address itself, where a link can point at
 it — the shape of a popup that is a LAYER over the screen, whose address is

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jsenv/navi",
-  "version": "0.29.457",
+  "version": "0.29.459",
   "type": "module",
   "description": "Library of components including navigation to create frontend applications",
   "repository": {