@jsenv/navi 0.29.513 → 0.29.514

package/dist/dev/jsenv_navi.js

@@ -38356,9 +38356,11 @@ const releaseTransitionDestination = (owner) => {
  * inside its rectangle — which is where the hand thinks it pressed. The same
  * move route_travel.jsx makes for the box a finger reaches for mid-flight.
  *
- * A `RouteTravel` holds this too. It leaves the bars live, so a control there
- * gets its click on its own; what this serves is a control in the part of a bar
- * photographed for the travel (`data-navi-fixed-bar-overhang`, fixed_bar.jsx).
+ * A `RouteTravel` holds this too, for the bars it leaves live. A control there
+ * gets its click on its own except in the first frames of the travel, when a
+ * press falls to the document root like any other; the part of a bar photographed
+ * for the travel (`data-navi-fixed-bar-overhang`, fixed_bar.jsx) is deaf
+ * throughout.
  *
  * ASKED FOR, never derived, and that is the whole safety of it: only the
  * application knows the control does not move. One that travels with the pages
@@ -39362,6 +39364,21 @@ const placeTransitionWindow = (owner, groupName) => {
   document.documentElement.setAttribute(WINDOW_PLACED_ATTRIBUTE, "");
 };
 
+/**
+ * Whether a point of the window lies in a band the furniture keeps: the pictures
+ * are cut at those bands, so what is seen there is never a page, however far the
+ * box runs under it.
+ */
+const isPointInTransitionBand = (clientX, clientY) => {
+  const band = readBand();
+  return (
+    clientX < band.left ||
+    clientX > window.innerWidth - band.right ||
+    clientY < band.top ||
+    clientY > window.innerHeight - band.bottom
+  );
+};
+
 // The live layout takes the box back. A discontinuity by construction — the
 // window stands at the held height, the box is at its own — and an invisible
 // one: the page arriving is fully in place, and the strip below it that the
@@ -42549,11 +42566,16 @@ const RouteTravel = ({
     gestureRef.current = gesture;
   };
 
-  // A press that lands ON the box while a travel is playing does not reach it:
-  // the browser's transition covers the page and the press is delivered to the
-  // document root instead, whatever the pictures are told about pointer events.
-  // So while a travel plays, the press is caught at the document and handed to
-  // the box when it fell inside it — which is where the hand thinks it pressed.
+  // A press aimed at a page while a travel is playing does not always reach the
+  // box: the browser's transition covers the page and the press can be delivered
+  // to the document root instead, whatever the pictures are told about pointer
+  // events. So while a travel plays, the press is caught at the document and
+  // handed to the box when it fell where a page is SEEN, which is where the hand
+  // thinks it pressed.
+  //
+  // Decided by the position and never by the target: in the first frames of a
+  // travel a press on a live bar falls to the root like any other, and what lies
+  // under a picture is not what the hand is aiming at.
   pointerDownRef.current = onPointerDown;
   useLayoutEffect(() => {
     const onDocumentPointerDown = pointerDownEvent => {
@@ -42578,6 +42600,11 @@ const RouteTravel = ({
       if (clientX < left || clientX > right || clientY < top || clientY > bottom) {
         return;
       }
+      // A box scrolled under a bar still has the press in its rectangle, but
+      // the pictures are cut at that bar: the press is aimed at the bar.
+      if (isPointInTransitionBand(clientX, clientY)) {
+        return;
+      }
       pointerDownRef.current(pointerDownEvent);
     };
     document.addEventListener("pointerdown", onDocumentPointerDown, true);
@@ -58011,8 +58038,9 @@ const LinkPseudoElements = ["::-navi-loader", "::-navi-indicator"];
  *   press on it is aimed at what the reader can see. Say it there, and only
  *   there: a control that TRAVELS with the pages has a rectangle where it will
  *   be, not where it is seen, and a press handed to it fires something nobody
- *   aimed at. A `RouteTravel` honours it as well, for a control in the part of
- *   a `FixedBar` it photographs (`data-navi-fixed-bar-overhang`).
+ *   aimed at. A `RouteTravel` honours it as well, for a control in a `FixedBar`:
+ *   the part it photographs (`data-navi-fixed-bar-overhang`) is deaf for the
+ *   whole travel, and the rest for its first frames.
  * @param {boolean} [props.replace] - Go to the destination by TAKING THE PLACE
  *   of the current history entry instead of stacking onto it: the link stays a
  *   link (an address, a middle click, the keyboard, `aria-current`), only the
@@ -64006,7 +64034,8 @@ const COMMAND_DEFAULT_PROPS_FACTORIES = {
  *   drawn — must still close it. What `<Link pressableDuringRouteTransition>`
  *   says, for the other half of a toggle. Only for a control that does not
  *   travel with the pages. A `RouteTravel` honours it as well, for a control in
- *   the part of a `FixedBar` it photographs (`data-navi-fixed-bar-overhang`).
+ *   a `FixedBar`: the part it photographs (`data-navi-fixed-bar-overhang`) is
+ *   deaf for the whole travel, and the rest for its first frames.
  * @param {Function} [action] What the press runs: a button holds no value, so
  *   every press is one call. Inside a `<Form>` or a group it carries the value
  *   around it, merged over the action's bound params — a value that is not an