@jsenv/navi 0.29.147 → 0.29.148

package/docs/popup_open.md

@@ -564,11 +564,19 @@ code inside knows whether anything in there loads at all:
 </Dialog>
 ```
 
-Without it the nearest boundary is the one at the root of the app, and a
-suspension there empties the whole page — taking with it the popup element the
-browser is in the middle of animating. The alternative is the component drawing
-its own wait (`useAsyncData(action, { loading: true })`), which needs no
-boundary; what is not an option is neither of the two.
+Without it the nearest boundary is one that holds the popup itself, and what
+happens then is worth knowing because nothing says it: the request goes out and
+**the popup does not open at all** — no fallback drawn, no error raised. A
+boundary waiting on an update keeps the page as it was, as a copy; the popup
+being opened is part of that copy, so `showModal()` reaches a node the app no
+longer owns, and once the data is there the subtree is rebuilt from scratch —
+closed, and empty. The press is simply lost, and the next one works. In dev the popup says so
+rather than leaving it to be guessed. The alternative is the component drawing its
+own wait (`useAsyncData(action, { loading: true })`), which needs no boundary of
+its own; what is not an option is neither of the two.
+
+Both, and what each one looks like, are on
+`src/layout/demos/13_popup_loading_demo.html`.
 
 What the popup gains is everything a page has:
 

package/docs/testid.md

@@ -99,6 +99,11 @@ and is the better name for a test that reads or clicks the content. Reach for
 `popupTestId` when the frame IS what the test looks at: a screenshot of the
 popup's surface, its position, its size, its backdrop.
 
+`<ControlSwap.Side>` answers the same situation the other way: the cap at the
+end of the row is drawn by navi, and every prop the side does not use for
+itself lands on it — so `data-testid` on the side names the cap, while what the
+side holds is a vnode of yours that takes its own.
+
 ## What not to target
 
 Navi's own attributes are implementation, not a contract: `data-header`,

package/package.json

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