@jsenv/navi 0.29.300 → 0.29.301

package/docs/interactions.md

@@ -98,6 +98,12 @@ which the carrying interactions answer with).
 | `pan` `zoom`                                           | a surface under the hand, or under a wheel                  |
 | `"keyboard:<shortcut>"`                                | keys, e.g. `"keyboard:ctrl+backspace"`                      |
 
+Two holds on one press — a `longpress` declared on something inside an
+element that declares one too — are answered by the nearer one, the way a
+click is the innermost target's: the inner hold fires, the outer wait is given
+up. Delays being equal; an outer hold made shorter than the inner one fires
+first.
+
 A name nothing knows how to detect produces a dev warning naming the detectors
 that exist. The carrying family and the two surface streams each have a file of
 their own — [drag_interactions.md](./drag_interactions.md) and

package/docs/popup_open.md

@@ -409,8 +409,9 @@ The picker's `action` runs on the trigger, not in the popup: it is dispatched
 on the close that keeps, and the popup goes while it runs. So what is still on
 screen answers for the write — `aria-busy` and the loading outline on the
 trigger while the request is out, the error callout on it if the server
-refuses, and the value rolled back to the last accepted one (`resetOnError`,
-on by default for a picker: nobody is left mid-edit behind a closed popup). A
+refuses, and the value rolled back to the last accepted one — on by default
+for a picker, and what one wants: nobody is left mid-edit behind a closed
+popup, and the card goes on saying what the server knows. A
 card that IS the trigger (`variant="bare"`, the card as `ui`) therefore waits
 as a card and is refused as a card, wherever in the tree the sheet was written.
 
@@ -422,9 +423,6 @@ as a card and is refused as a card, wherever in the tree the sheet was written.
   ui={<MatchCard match={match} />}
   value={match}
   action={(next) => MATCH.PATCH({ id: match.id, ...next })}
-  // the draft is what the person typed, and the sheet is the only place it
-  // can be found again: keep it when the server says no
-  resetOnError={false}
 >
   <ControlGroup>
     <MatchCard match={match} editable />
@@ -434,6 +432,16 @@ as a card and is refused as a card, wherever in the tree the sheet was written.
 </Picker>
 ```
 
+The card shows the answer the moment the sheet leaves when its `ui` is drawn
+from what the picker holds rather than from what the caller knows — the same
+state navi's own default `ui` reads, rolled back by `resetOnError`, so nothing
+about the pending value is the caller's to keep or to put back. Two ways to
+read it: `ui={MatchCard}` hands the component `value`, `loading` and
+`interactive` as props; `ui={<MatchCard match={match} />}` keeps the caller's
+own props and reads the same three with `usePickerState()` inside. The
+`loading` is the wait: navi's loading outline is a two-pixel run around the
+box, which a card-sized trigger draws its own waiting state for.
+
 What the picker measures as "changed since open" is what its mirrored group
 holds. A piece of the answer living outside the controls — a seating
 rearranged by drag, kept in component state — has to be held by a control in
@@ -442,8 +450,19 @@ as nothing changed and nothing runs.
 
 Two props finish the construct. `openOn="longpress"` (or
 `["longpress", "contextmenu"]`) makes the hold what opens it, so a tap on the
-card stays a tap — what a card in a list needs. `animation="growing"` with
-`dialogSizeFromAnchor`, `dialogMaxWidth="var(--anchor-width)"`,
+card stays a tap — what a card in a list needs: the drawing gets its pointer
+back, a link in it navigates, a button in it presses, a picker in it opens on
+its own click, with nothing to declare. Two pickers on one card is the score
+sheet inside the edit card (`12_picker_card_demo.html`): the inner one names
+the card as its `anchor` so it lifts the whole card, and says `standalone` so
+its value stays its own. One card, one wait: each picker wears the other's
+run through `loading` (from its `onActionStart`/`onActionEnd`), so while
+either write is out the hold and the click are both refused, with the busy
+reason where the finger is — the click only once the score picker says
+`openWhileReadOnly={false}`: a busy picker otherwise still opens, to be read,
+and a sheet of fields to fill in is not that. A hold declared inside the card answers before the
+card's own: the nearer hold takes the press. `animation="growing"` with
+`dialogSizeFromAnchor` (as wide as the card, floor and ceiling),
 `popupBackgroundColor="transparent"` and `popupBoxShadow="none"` lifts the
 card out of its place and puts it back (`data-grow` on the card inside the
 sheet; see Dialog's own `animation`). `12_picker_card_demo.html` shows all of

package/package.json

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