@jsenv/navi 0.30.1 → 0.30.4

package/docs/dialog_shape.md

@@ -55,6 +55,9 @@ covers anything else behind that sheet. Once back on top it answers the screen
 as it is: at once when the focus landed on a field, since the keyboard stays;
 once the keyboard has left otherwise, so it never jumps up and back down. What
 sits under a non-modal dialog is still usable, and keeps following the keyboard.
+A `layer="top"` `Popover` covered by a modal dialog is held the same way, but it
+holds nothing itself: it may be anchored inside what is below it, and what is
+below rising is what carries a field in the popover above the keyboard.
 
 ## One dialog, two shapes
 

package/docs/navigation.md

@@ -578,19 +578,22 @@ so, and a page brought in stands where the reader is looking; what is lost is
 **The URL can say where the hand is heading, not where the reader is.** For a page
 that is not there yet, a page of a window or a tab never visited, it changes once
 the hand has really pulled, and comes back if the page is let go of. A tab already
-built waits for the landing. So a counter, a title or a breadcrumb around the box
-reads `routeTravelSettledPageSignal` first, or it moves for a pull that goes
-nowhere:
+built waits for the finger to lift. A link to a page of the row answers for the page
+held while the hand holds it, whatever the URL says. A counter, a title or a
+breadcrumb around the box reads `routeTravelSettledPageSignal` first, or it moves
+for a pull that goes nowhere:
 
 ```jsx
 const settledPage = routeTravelSettledPageSignal.value;
 const shownId = settledPage ? settledPage.params.gameId : currentId;
 ```
 
-It holds the `{ route, params }` the hand set off from, and is `null` when the row
-has come to rest, the URL being the truth again. A tab pressed holds nothing, and
-`null` is all it ever reads. One signal for the document: on a page with several
-boxes, `route` says which row it is.
+It holds the `{ route, params }` the hand set off from, and is `null` from the moment
+a lifted finger leaves the row moving, the URL being the truth again: the row is only
+playing out what the browser decided. A trackpad has no lift, so there it lasts until
+the row has come to rest, and a tab already built waits for that too. A tab pressed
+holds nothing, and `null` is all it ever reads. One signal for the document: on a
+page with several boxes, `route` says which row it is.
 
 `RouteTravel` is for pages that form a ROW the finger can push; pages related
 pair by pair are animated with `defineRouteTransition`, and a given pair by one

package/docs/scroll.md

@@ -254,6 +254,14 @@ list warns in dev when the second is missing:
 A row selected during the search does not hold the view: emptying the search
 takes the list back to where it was, which may be nowhere near that row.
 
+The offset is given back once, in the frame after the search empties, and then
+forgotten. A list under a `display: none` at that moment cannot scroll, so it has
+nowhere to put it: shown again, it stands at its start, and the `navi_scroll` of
+that restore carries no `item`. It does not wait to be shown, because the user
+may have moved on by then, and an old offset would surprise them more than the
+start of the list. A list that is only out of view still gets its offset back. To
+keep the place across a hide, empty the search once the list is shown again.
+
 ### Loading: two different situations
 
 `loading` (with `loadingFallback`, `loadingSkeletonCount`, `renderSkeleton`)

package/package.json

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