@jsenv/navi 0.29.518 → 0.29.519

package/docs/interactions.md

@@ -409,9 +409,8 @@ this element's to block.
 A greyed cross that still removes is worse than no cross — hence the default.
 `"ignore"` is the other extreme and the caller owns it: answering "read-only" to
 a gesture that was never going to write says nothing true, so use it only when
-that is really the case. navi's `<Dialog.Close />` is one — leaving what a
-read-only picker opened writes nothing to it — and a hand-written cross must say
-the same, or it refuses the way out (see
+that is really the case. A way out needs no claim: a button saying `--navi-close`
+or `--navi-cancel` with no action is not reached by the zone at all (see
 [popup_open.md](./popup_open.md#the-close-cross)).
 
 Busy is not on the list because busy does not block: it is the read-only a

package/docs/network_policy.md

@@ -139,8 +139,9 @@ stays pressable — a travel between slides or a step back in a wizard
 "Cancel", `ButtonCopyToClipboard`) — and so is a way out (`--navi-close`,
 `--navi-cancel`). The same goes for what a held control holds: a `Link` in the
 popup of a held `Picker` still leads to its page. The form's own read-only and
-busy state hold them all the same; `whenSelfInteractionsBlocked="ignore"` is what
-takes a button out of those too.
+busy state hold them all the same, a way out apart;
+`whenSelfInteractionsBlocked="ignore"` is what takes any other button out of those
+too.
 
 ## Holding writes while reads go out
 

package/docs/popup_open.md

@@ -657,22 +657,14 @@ The text of the row is the popup's title, and so its name (see
 
 ### It is the way out, so the state around it does not reach it
 
-**A close button written by hand refuses the press inside a read-only control.**
-A read-only `Picker` still opens, to be read, and hands its popup that same
-read-only. Closing writes nothing to the picker, and `<Dialog.Close />` says so
-(`whenSelfInteractionsBlocked="ignore"`, see
-[interactions.md](./interactions.md#where-the-zone-blocks-does-it-write-to-the-control-it-sits-in));
-a `<Button command="--navi-close" />` does not, wears the read-only it was
-handed, and answers a press aimed at the way out with "this action is not
-available right now". The same holds for a disabled zone and for a form busy
-sending: the way out of a popup is never held by the state of what the popup
-belongs to. A cross that really has to be hand-written carries the claim itself:
-
-```jsx
-<Button command="--navi-close" icon whenSelfInteractionsBlocked="ignore">
-  …
-</Button>
-```
+**The way out of a popup is never held by the state of what the popup belongs
+to.** A read-only `Picker` still opens, to be read, and hands its popup that same
+read-only, yet closing writes nothing to the picker. So a button or a link saying
+`--navi-close` or `--navi-cancel`, with no `action` of its own, stays pressable
+in a read-only, disabled or busy zone, written by hand or not, the same as
+`<Dialog.Close />`. The picker agrees: one that turns read-only, disabled or busy
+while its popup is open still lets it close, `openWhileReadOnly={false}` included,
+since that prop is about opening.
 
 ### It asks, it does not force
 

package/package.json

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