@jsenv/navi 0.29.167 → 0.29.169

package/docs/interactions.md

@@ -790,6 +790,16 @@ container above it does not take the gesture:
   the browser's menu. Declare `contextmenu` beside it to make the right click do
   the same thing. (A held _finger_ is the system's own context-menu gesture, and
   that one is refused while the wait runs.)
+- **Where the press already means something, text is not selected.** An element
+  declaring `longpress` or a swipe, and a drag source standing in a
+  `data-drag-on-contact` place, keep their text unselectable: the browser answers
+  that same press with a selection of its own — the word under the thumb, blue,
+  with handles — and nothing takes it back once the press is over. For every
+  pointer, mouse included, which cannot finish a selection begun where the press
+  is a gesture. What never answered that press keeps its text: a field, a popover
+  or a dialog opened from inside, and anything marked `data-drag-ignore`. A drag
+  source taken by long press is not concerned — the grab happens first, and the
+  gesture refuses the selection for its own length.
 - **A swipe cannot also be dragged out of the page.** An element declaring a
   swipe gets `draggable={false}` and its `dragstart` refused — a native drag _is_
   press-and-move, and a link or an image is draggable without anyone asking. One

package/docs/popup_open.md

@@ -396,6 +396,13 @@ an abort — leaves the popup where it is. Same rule a form already follows for
 what comes after its send (`data-after-send`, see `resolveAfterSend` in
 commands.js).
 
+The action is free to replace that button while it runs — and it usually does:
+what came back is put in the store, the tree re-renders, and the branch the
+button stood in goes with it. The popup closes all the same. What the command
+aims at is read at the press, while the button is still in the document (see
+`resolveNaviCommand` in commands.js); only the running of it waits. The popup
+pressed in is the popup that closes, even when the press is what emptied it.
+
 The wait is why closing **from inside** the action still does not close: while
 the action runs, the button that started it is busy, and a busy control is
 exactly what a popup refuses to close over (see the top of this page). The

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jsenv/navi",
-  "version": "0.29.167",
+  "version": "0.29.169",
   "type": "module",
   "description": "Library of components including navigation to create frontend applications",
   "repository": {
@@ -29,7 +29,7 @@
     "prepublishOnly": "npm run build"
   },
   "dependencies": {
-    "@jsenv/dom": "0.17.38",
+    "@jsenv/dom": "0.17.40",
     "@jsenv/humanize": "1.7.8",
     "@jsenv/validity": "0.4.3"
   },