@jsenv/navi 0.29.487 → 0.29.489

package/docs/navigation.md

@@ -386,6 +386,11 @@ local state down through `elementProps`. Pages sharing a layout but no prefix
 (`/profile`, `/settings`) use a container `<Route element={AuthLayout}>`, which
 injects the active child as its children.
 
+A page names itself with its own `<Head><title>…</title></Head>`, rendered with
+the page: the last `<Head>` mounted holds the document title and the theme
+colour, and one that renders again keeps its place, so a layout's `<Head>` is a
+default under every page.
+
 ### Loading data
 
 A page reads its data from a route action through `useAsyncData` and says only

package/docs/popup_open.md

@@ -729,9 +729,13 @@ what varies while it is open (a tab inside it) is a param of its own, see
 The other way round — ONE sheet showing whichever card the address names — is
 the same signal with no `value`: anything but `false`, `null` and `undefined`
 reads as open, opening writes `true` only into a signal that reads closed, and
-closing writes `undefined` (`false` where it held `true`). The content reads the
-id from the signal and a card's press writes it — in `onOpen` when the popup is
-opened ON the card, which runs before the popup writes its own open. With the
+closing writes `undefined` (`false` where it held `true`). A card's press writes
+the id — in `onOpen` when the popup is opened ON the card, which runs before the
+popup writes its own open — and the content reads it with `usePopupValue()`,
+not from the signal: the signal reads closed as soon as the close starts, while
+an animated exit, and a lifting close flying back to the card, still draw what
+the content renders. `usePopupValue()` holds the id the popup is open on until
+the next opening, and `liftAnchor` takes a function of it. With the
 route's search-param `stateSignal` as the signal, that is how
 [a row of cards](./popup_lift.md#a-row-of-cards-one-popup-that-walks) survives
 leaving the page: the address names the card, and the sheet reopens on it.

package/docs/resource.md

@@ -645,7 +645,7 @@ const ROLE_WITH_OWNERS = ROLE.withParams(
 
 Any write on a listed resource (`POST`, `PUT`, `PATCH`, `DELETE`) reruns the
 completed `GET` and `GET_MANY` of the resource that declared it, and invalidates
-its `GET_RANGE` readers when the verb is in its `rerunOn.GET_RANGE`. A
+its `GET_RANGE` readers: its own `rerunOn` is about its own writes. A
 dependency is a facade: `DATABASE` and `DATABASE.withParams(…)` are two of them,
 and only writes on the one listed count. Nothing goes the other way, and nothing
 is inferred — a relation that really is a sub-route of the parent is modelled

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jsenv/navi",
-  "version": "0.29.487",
+  "version": "0.29.489",
   "type": "module",
   "description": "Library of components including navigation to create frontend applications",
   "repository": {
@@ -34,7 +34,7 @@
     "preact": "^11.0.0-rc.2"
   },
   "dependencies": {
-    "@jsenv/dom": "0.17.96",
+    "@jsenv/dom": "0.17.97",
     "@jsenv/humanize": "1.8.10",
     "@jsenv/validity": "0.4.7"
   },