@jsenv/navi 0.29.419 → 0.29.420

package/docs/create_and_edit.md

@@ -215,6 +215,16 @@ By hand this is a `useEffect` keyed on `game?.id` — `[game]` is the natural,
 wrong, thing to write — and a passive effect is too late: the screen opens
 **already changed**, and Save sends the resource back untouched.
 
+`defaultValue={game?.name}` on the fields needs no copy — a field follows a new
+default while it holds no edit
+([control_value.md](./control_value.md#a-defaultvalue-follows-what-it-was-read-from))
+— and fails the same way: a default is a suggestion the form does not hold, and
+confirming one is an answer
+([form_changed.md](./form_changed.md#what-counts-as-already-held)), so the
+untouched game goes out on the first Save. What the copy gives up is that
+follow: a game moved while the screen is open stays as `onLoad` found it — which
+a screen left on saving, and copied afresh when it opens again, can afford.
+
 **Or the screen waits, showing nothing of the form**: a skeleton until the
 resource is there, then the form holding its values from its first render —
 for a screen that can be blanked without the person losing their place.

package/docs/data_states.md

@@ -73,14 +73,13 @@ means something different:
 whose params name a row the store already holds — read earlier by a `GET_MANY`,
 a relation, a list — starts on the second line, not the first: the row is
 drawn, the request goes out behind it, and a failure lands beside it like any
-refresh failure. A row known from the previous page load counts too, when the
-resource asks for it:
+refresh failure. A `GET` of a row the store lacks starts on the first line, so
+what is drawn is never a different row — a `GET` bound through a signal (a route
+action, a `bindParams` holding one) included, when the signal moves to other
+params. A row known from the previous page load counts too, when the resource
+asks for it:
 [`persist`](./resource.md#persist-the-last-answer-drawn-again-after-a-reload)
-puts a reload on the second line as well. A `GET` bound through a signal — a
-route action, a `bindParams` holding one — is on the second line when the signal
-moves to params it has not answered yet, with the previous params' row: its
-`data` stays that row until the new answer lands, whether or not the store holds
-the new one.
+puts a reload on the second line as well.
 
 **The emptiness test is `data === undefined`, never `loading`.** Reading
 `loading` as "there is nothing to display" blanks the screen on every refresh —

package/docs/form_changed.md

@@ -16,9 +16,11 @@ later.
 
 ## Sending nothing is the default
 
-Submitting a form nobody touched — one just rendered, one whose fields still
-hold their defaults, one reopened and left alone — runs **no action**. No
-request, nothing in the network tab.
+Submitting a form nobody touched — one just rendered, one reopened and left
+alone — runs **no action**. No request, nothing in the network tab. The
+exception is a field still showing its `defaultValue`: confirming a suggestion
+is an answer, sent once (see
+[What counts as already held](#what-counts-as-already-held)).
 
 Everything around the action still happens: the constraints are checked, and
 what follows the send still follows it — the popup closes, the slide moves on,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jsenv/navi",
-  "version": "0.29.419",
+  "version": "0.29.420",
   "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.85",
+    "@jsenv/dom": "0.17.86",
     "@jsenv/humanize": "1.8.6",
     "@jsenv/validity": "0.4.5"
   },