@jsenv/navi 0.29.513 → 0.29.515

package/docs/route_transitions.md

@@ -320,8 +320,9 @@ finger is on the box — and leaves the bars live, so its pictures cover what a
 paints outside its box, except two things photographed on their own, which stand
 over the pages: the bar's `shadow`, and a child wearing
 `data-navi-fixed-bar-overhang` (a raised button, the notch around it). That child
-is deaf for the length of the travel; `pressableDuringRouteTransition` on a control
-inside it keeps that control answering.
+is deaf for the length of the travel, and the rest of the bar for its first frames,
+when a press falls to the document whatever it was aimed at;
+`pressableDuringRouteTransition` on a control keeps it answering in both cases.
 
 A **modal `Dialog` open on a page** is furniture of the same kind: it travels with
 its page, or holds if both states have it. One the navigation itself opens or

package/docs/scroll.md

@@ -163,6 +163,37 @@ again a frame later. `:smooth` glides, and is instant under
 `scroll-behavior`: a `scroll-behavior: smooth` on the box glides every
 placement of the list, the one it opens on included.
 
+The `id` is on the list's outer box, which is not the box that scrolls: which one
+does depends on `scroller` and on what can be measured (see
+[above](#list-and-its-scroller)). So a list is moved through these, never through
+`scrollTo` on an element of its DOM, and a "back to top" button is
+`command="--navi-scroll" value="start"`.
+
+### Another order, another filter: back to the start
+
+A list showing something else is read from its start. `scrollResetKey` says what
+that depends on:
+
+```jsx
+<List id="players_list" scrollResetKey={[listKey, order]}>
+  …
+</List>
+```
+
+When the value changes after mount (compared by value, so an array can be written
+at every render), the list goes back to its start in the box `scroller` names,
+before the paint, and stays there while answers land, until the user reaches for
+it. Its window moves in the same render: nothing is drawn or fetched at the place
+it leaves. Mounting is not a change, so the list still comes back where it was
+left.
+
+- **Its start is what is brought back, never sent forward.** A list further down a
+  box or a page that also shows what stands above it does not move when its start
+  is in view: the picker above it stays on screen.
+- **The position kept under its `id`** is dropped for the address shown, so a
+  return finds the list at its start. A key that is also a search param changes
+  the address: the address left keeps its position, for a return to it.
+
 ### A list that comes back: one `id`, one list
 
 The position a list comes back to is kept under its `id` and the page's url, so

package/package.json

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