@jsenv/navi 0.29.517 → 0.29.519

package/dist/dev/jsenv_navi.js

@@ -22024,6 +22024,11 @@ const BUSY_CONSTRAINT = {
       return null;
     }
 
+    // Same as READONLY_CONSTRAINT: a run inside the popup holds it from there.
+    if (intent === "close") {
+      return null;
+    }
+
     // Busy, and what it opens still opens: a picker's answer lives in a shape
     // only its popup draws, and refusing to open leaves it unreadable for as
     // long as the wait lasts. Opening reads and nothing more — the same
@@ -22118,12 +22123,17 @@ const findBusySource = (field) => {
 const DISABLED_CONSTRAINT = {
   name: "disabled",
   messageAttribute: "data-disabled-message",
-  check: (field) => {
+  check: (field, { intent } = {}) => {
     const disabled = field.controlHostProps.disabled;
     if (!disabled) {
       return null;
     }
 
+    // Same as READONLY_CONSTRAINT: a popup still open leaves like any other.
+    if (intent === "close") {
+      return null;
+    }
+
     const type = field.controlHostProps.type;
     let message;
     if (type === "radio") {
@@ -23112,6 +23122,14 @@ const READONLY_CONSTRAINT = {
       return null;
     }
 
+    // Leaving a popup already open is never the control's to refuse, whatever
+    // it would refuse on the way in: closing writes nothing, and what may hold
+    // a popup is the popup's own question (see popup_busy.js and the picker's
+    // onRequestClose).
+    if (intent === "close") {
+      return null;
+    }
+
     // Read-only, and what it opens still opens: a picker's answer often lives
     // in a shape only its popup draws — a plan with one tile ringed, a wheel
     // stopped on a time — and refusing to open leaves that shape unreadable.
@@ -23211,7 +23229,8 @@ const readOnlyMessage = (field) => {
  *   → onRequestInteraction
  *       → check disabled / read-only / busy (via controller.rules.interaction)
  *         against the interaction's `intent` ("write" by default, "read" for one
- *         that only shows what is already there — see READONLY_CONSTRAINT)
+ *         that only shows what is already there, "close" for one leaving a popup
+ *         — see READONLY_CONSTRAINT)
  *       → if blocked  → prevented()
  *       → if allowed  → allowed()
  *         → (in allowed callback) setUIState(value)
@@ -23494,9 +23513,10 @@ const onRequestInteraction = (
     name,
     // What this interaction would do to the control: write it, or only read it.
     // Everything writes unless it says otherwise — an interaction that merely
-    // shows what is already there (opening a picker's popup, closing it again)
-    // says "read", and that is what a control held read-only can still let
-    // through (see READONLY_CONSTRAINT).
+    // shows what is already there (opening a picker's popup) says "read", and
+    // that is what a control held read-only can still let through. Closing that
+    // popup says "close", which no state of the control refuses (see
+    // READONLY_CONSTRAINT).
     intent = "write",
     bypassInteractivity = false,
     // navi continuing a gesture on its own rather than a user asking for
@@ -39834,12 +39854,6 @@ const css$17 = /* css */`@property --navi-route-transition-leave {
   inherits: false
 }
 
-@property --navi-furniture-fade {
-  syntax: "<number>";
-  inherits: true;
-  initial-value: 1;
-}
-
 :root::view-transition, :root::view-transition-group(*), :root::view-transition-image-pair(*), :root::view-transition-old(*), :root::view-transition-new(*) {
   --navi-route-transition-leave: inherit;
   --navi-route-transition-enter: inherit;
@@ -39922,22 +39936,14 @@ const css$17 = /* css */`@property --navi-route-transition-leave {
       animation-duration: var(--navi-route-transition-duration, .3s);
     }
 
-    &::view-transition-image-pair(.navi_furniture_shared) {
-      animation: navi-furniture-fade
-          var(--navi-route-transition-duration, .3s) ease both;
-    }
-
-    &::view-transition-old(.navi_furniture_shared), &::view-transition-new(.navi_furniture_shared) {
-      mix-blend-mode: plus-lighter;
-      animation-name: none;
-    }
-
     &::view-transition-old(.navi_furniture_shared) {
-      opacity: calc(1 - var(--navi-furniture-fade));
+      mix-blend-mode: plus-lighter;
+      animation-name: navi-route-transition-fade-out;
     }
 
     &::view-transition-new(.navi_furniture_shared) {
-      opacity: var(--navi-furniture-fade);
+      mix-blend-mode: plus-lighter;
+      animation-name: navi-route-transition-fade-in;
     }
   }
 
@@ -40215,6 +40221,10 @@ const css$17 = /* css */`@property --navi-route-transition-leave {
 }
 
 @keyframes navi-route-transition-fade-out {
+  from {
+    opacity: 1;
+  }
+
   to {
     opacity: 0;
   }
@@ -40224,15 +40234,9 @@ const css$17 = /* css */`@property --navi-route-transition-leave {
   from {
     opacity: 0;
   }
-}
-
-@keyframes navi-furniture-fade {
-  from {
-    --navi-furniture-fade: 0;
-  }
 
   to {
-    --navi-furniture-fade: 1;
+    opacity: 1;
   }
 }
 `;
@@ -44764,11 +44768,8 @@ const clearCommand = (source, event) => {
       return;
     }
     // Only what is open: the clear cross of a picker sits on the closed
-    // trigger, and asking that trigger to close is asking it to do nothing —
-    // except that the ask goes through the interaction gate, which turns it
-    // down while the clear it just sent is still running and says so out loud
-    // ("this element is busy"). A clear pressed INSIDE an open popup is the
-    // one this is for: it answers the popup, so the popup goes away.
+    // trigger, with nothing to close. A clear pressed INSIDE an open popup is
+    // the one this is for: it answers the popup, so the popup goes away.
     const expandable = resolveClosestExpandable(source);
     if (expandable?.getAttribute("aria-expanded") !== "true") {
       return;
@@ -53171,21 +53172,20 @@ const useInteractiveProps = (props, {
     // — a diskette saving a row into the reader's own address book stays
     // pressable on a game nobody may edit. Its own props still hold; only what
     // came from above is dropped (see self_interactions.js for the three modes).
-    const zoneStateApplies = !selfInteractionsIgnoreBlock(props);
     // A press that only leaves the popup it sits in writes nothing to the zone
-    // around it either, so that zone being read-only — or holding a write the
-    // network policy keeps — does not hold it: the popup answers the close
-    // itself. A read-only picker's popup then closes from its own button as
-    // it does from a press outside, and refuses both alike when it holds a
-    // change it cannot send.
-    const zoneReadOnlyApplies = zoneStateApplies && !pressOnlyLeaves(props);
+    // around it either, so that zone being disabled, read-only or busy — or
+    // holding a write the network policy keeps — does not hold it: the popup
+    // answers the close itself. A read-only picker's popup then closes from its
+    // own button as it does from a press outside, and refuses both alike when it
+    // holds a change it cannot send or a run it cannot give up on.
+    const zoneStateApplies = !selfInteractionsIgnoreBlock(props) && !pressOnlyLeaves(controlInfo.controlType, props);
     // A press feeding nothing to the write around it — a travel, a page, a
     // uiAction, a function of its own — has nothing for the network policy to
     // keep: only its own verb holds it, as anywhere else. What the zone holds
     // for its own reasons (read-only, busy) still holds it.
     const asksNothingOfTheWrite = pressAsksNothingOfTheWrite(controlInfo.controlType, props, boundAction);
     const controlDisabled = zoneStateApplies && controlDisabledFromAbove;
-    const controlReadOnly = zoneReadOnlyApplies && !(asksNothingOfTheWrite && controlReadOnlyFromAbove === "network-policy") && controlReadOnlyFromAbove;
+    const controlReadOnly = zoneStateApplies && !(asksNothingOfTheWrite && controlReadOnlyFromAbove === "network-policy") && controlReadOnlyFromAbove;
     const controlLoading = zoneStateApplies && controlLoadingFromAbove;
     const disabledResolved = disabled || controlDisabled;
     const requiredResolved = required || controlRequired;
@@ -53204,7 +53204,7 @@ const useInteractiveProps = (props, {
     // picker's popup) — refuses before the press and says why (see
     // network_policy.js): a press that looks accepted and fails after is what
     // the policy exists to avoid.
-    const heldByNetworkPolicy = networkPolicyReason !== null && (isWriteAction(boundAction) || Boolean(zoneReadOnlyApplies && !asksNothingOfTheWrite && parentAction && isWriteAction(parentAction)) || controlReadOnly === "network-policy");
+    const heldByNetworkPolicy = networkPolicyReason !== null && (isWriteAction(boundAction) || Boolean(zoneStateApplies && !asksNothingOfTheWrite && parentAction && isWriteAction(parentAction)) || controlReadOnly === "network-policy");
     // Held back because the surface above already has as many runs in flight as
     // it allows (see parallel_guard.js). Only a control that would START one:
     // anything without an action of its own runs nothing and has nothing to
@@ -53778,10 +53778,11 @@ const splitControlProps = (props, {
   return [controlRootProps, controlHostProps];
 };
 // What a press leaving a popup asks for: closing it, or cancelling it. Only on
-// a control running nothing of its own — one with an action writes, wherever
-// it then leads.
+// a button or a link running nothing of its own — one with an action writes,
+// wherever it then leads, and on a field or a form `command` is what follows
+// the value it writes.
 const LEAVING_COMMAND_SET = new Set(["--navi-close", "--navi-cancel"]);
-const pressOnlyLeaves = props => LEAVING_COMMAND_SET.has(props.command) && !props.action;
+const pressOnlyLeaves = (controlType, props) => (controlType === "button" || controlType === "link") && LEAVING_COMMAND_SET.has(props.command) && !props.action;
 // What these commands move reads only the person's place: the slide shown,
 // the item pointed at, the scroll, the page (see commands.js).
 const COMMANDS_ASKING_NOTHING_OF_THE_WRITE = new Set(["--navi-right", "--navi-left", "--navi-down", "--navi-up", "--navi-previous", "--navi-next", "--navi-first", "--navi-last", "--navi-go-to-slide", "--navi-back", "--navi-scroll", "--navi-nav-to", "--navi-nav-back"]);
@@ -57859,6 +57860,7 @@ const css$$ = /* css */`@layer navi {
   }
 
   &[data-stretch] {
+    z-index: auto;
     position: static;
 
     &:after {
@@ -76297,12 +76299,11 @@ const clipOf = (side, distance) => {
  * `--navi-close`, which the nearest popup above it answers; the caller only
  * decides where it goes (the right end of a header, most of the time).
  *
- * It is the way out of a popup, so it is the one affordance in there that the
- * surrounding control's read-only and disabled do not reach: a read-only picker
- * still opens (reading changes nothing) and hands its popup that read-only, and
- * a cross wearing it would trap the user in a popup they were invited to read.
- * A close button written by hand inherits it and refuses the press — which is
- * the reason to use this one rather than a `<Button command="--navi-close" />`.
+ * It is the way out of a popup, so the state of the surrounding control does not
+ * reach it, as with any `--navi-close` button that has no action of its own (see
+ * pressOnlyLeaves in control_hooks.jsx): a read-only picker still opens (reading
+ * changes nothing) and hands its popup that read-only, and a cross wearing it
+ * would trap the user in a popup they were invited to read.
  *
  * Exempt from the state around it, never from the popup's own answer: the cross
  * ASKS, and the popup decides — a dialog holding a form mid-send keeps the
@@ -76329,15 +76330,6 @@ const PopupClose = ({
     command: "--navi-close",
     icon: true,
     variant: "discrete"
-    // Dismissing writes nothing to whatever control the popup belongs to, so
-    // that control's read-only and disabled are not about this cross: a
-    // read-only picker still opens to be read (see readonly_constraint.js),
-    // and what is opened has to be closable. Whether closing is allowed at
-    // this instant is the popup's own question, answered by the popup — a
-    // dialog holds the close while an action inside it runs (see
-    // popup_busy.js).
-    ,
-    whenSelfInteractionsBlocked: "ignore"
     // The cross is drawn at the control size, which is a few millimetres
     // wide; the padding is what makes it a target a thumb can hit.
     ,
@@ -82036,11 +82028,11 @@ const PickerCustom = props => {
           event: e,
           name: "navi_request_open_event",
           // Showing what the picker already holds, in the shape only the popup
-          // draws it in — nothing of the value is written on the way in, nor on
-          // the way out. Every interaction below says the same, which is what
-          // lets a read-only picker be opened and read while everything that
-          // would write it (paste, cut, the clear cross) stays refused. See
-          // READONLY_CONSTRAINT.
+          // draws it in — nothing of the value is written on the way in. Every
+          // way of opening below says the same, which is what lets a read-only
+          // picker be opened and read while everything that would write it
+          // (paste, cut, the clear cross) stays refused. Every way of closing
+          // says "close". See READONLY_CONSTRAINT.
           intent: "read",
           allowed: () => {
             // What the open said travels with it: a picker opened from
@@ -82065,7 +82057,7 @@ const PickerCustom = props => {
       onnavi_request_close: e => {
         requestInteraction({
           event: e,
-          intent: "read",
+          intent: "close",
           allowed: () => {
             const closing = requestClose(e, {
               isCancel: e.detail.isCancel,
@@ -82172,7 +82164,7 @@ const PickerCustom = props => {
           }
           return {
             name: "escape_to_cancel",
-            intent: "read",
+            intent: "close",
             allowed: () => {
               // Read with escapeEffect by the controller (see above).
               requestClose(e, {
@@ -82249,7 +82241,7 @@ const PickerCustom = props => {
               pressAnsweredAtMouseDownRef.current = readPressCount();
               return {
                 name: "mousedown to close picker",
-                intent: "read",
+                intent: "close",
                 allowed: () => requestClose(e, {
                   isCancel: true
                 })
@@ -82297,7 +82289,7 @@ const PickerCustom = props => {
             if (openController.opened && !openedDuringThisPress(openController)) {
               return {
                 name: "click to close picker",
-                intent: "read",
+                intent: "close",
                 prevented: () => {
                   e.preventDefault();
                 },