@jsenv/navi 0.29.456 → 0.29.458

package/docs/dynamic_import.md

@@ -145,6 +145,24 @@ that asks for nothing (`() => true`).
 `routeAction(route, action, undefined, { prefetch: false })` keeps a param-less
 read that is not worth a hover out of it.
 
+A page only some readers may download keeps its condition out of the params and
+says it with `when`: a condition on app state, not on the address, so the link
+still prefetches the action, as long as the condition holds when the pointer
+arrives. A reader for whom it does not hold downloads nothing, not even by
+typing the address.
+
+```js
+const VIDEO_PAGE_CODE = routeAction(
+  VIDEO_ROUTE,
+  () => import("./video_page.jsx").then((m) => m.VideoPage),
+  undefined,
+  { when: () => meIsAdminSignal.value },
+);
+```
+
+The link reads `when` as it is at that moment, not as the address it leads to
+will make it: a condition that reads the address belongs in the params.
+
 A prefetch that fails is not reported: nothing on screen asked for it. The failure
 stays on the action, and a failed action is run again by whatever asks next — the
 arrival, which shows its own failure, and every later hover alike.

package/docs/interactions.md

@@ -122,6 +122,33 @@ how to detect gets a dev warning naming the detectors that exist. The carrying
 family and the surface have a file each:
 [drag_interactions.md](./drag_interactions.md) and [pan_zoom.md](./pan_zoom.md).
 
+A declared key takes the key: the browser's default for it does not happen as
+well, whether the gate lets it through or refuses it. On a field this includes
+the field's own keys — the caret, typing — so a text field can say what its
+arrows do, through the same gate as a number field's:
+
+```jsx
+const step = (event, seconds) => {
+  const input = findEvent(event, "keydown").target;
+  const next = formatTime(parseTime(input.value) + seconds);
+  dispatchRequestSetUIState(input, next, { event });
+};
+
+<Input
+  value={formatTime(start)}
+  interactions={{
+    "keyboard:arrowup": (event) => step(event, 1),
+    "keyboard:arrowdown": (event) => step(event, -1),
+    "keyboard:shift+arrowup": (event) => step(event, 60),
+    "keyboard:shift+arrowdown": (event) => step(event, -60),
+  }}
+/>;
+```
+
+A shortcut is matched with its exact modifiers, so Shift is a key of its own.
+Keys declared on something around a field — a list item, a row — leave the
+field inside every key it has a use for.
+
 ## Which interaction asked
 
 An interaction navi makes is **dispatched as an event of its own name** —

package/package.json

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