@jsenv/navi 0.29.361 → 0.29.363

package/docs/popup_open.md

@@ -434,7 +434,8 @@ as a card and is refused as a card, wherever in the tree the sheet was written.
 
 The card shows the answer the moment the sheet leaves when its `ui` is drawn
 from what the picker holds rather than from what the caller knows — the same
-state navi's own default `ui` reads, rolled back by `resetOnError`, so nothing
+state navi's own default `ui` reads, rolled back by `resetOnError` (and
+`resetOnAbort`), so nothing
 about the pending value is the caller's to keep or to put back. Two ways to
 read it: `ui={MatchCard}` hands the component `value`, `loading` and
 `interactive` as props; `ui={<MatchCard match={match} />}` keeps the caller's

package/docs/scroll.md

@@ -157,6 +157,12 @@ picked up then. When it is still not the box you mean, say so explicitly with
   `open`/`defaultOpen` elsewhere in navi. The list goes back there every time it
   changes, even after the user scrolled.
 - **`onScrolledChange`** gives `{id, index, offset}` as the user scrolls.
+- A list with an `id` **comes back where it was** when its screen is left and
+  come back to, the way the page does: the position is kept under the list's
+  `id` and the page's url, for the session, and put back by name the way
+  `defaultScrolled={{id, offset}}` is. A fresh arrival at the page still opens
+  at `defaultScrolled`. **`scrollResetOnNavigation`** opts out: the list then
+  opens the same way every time.
 
 ### A search moves the list, and gives it back
 

package/package.json

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