@jsenv/navi 0.29.512 → 0.29.514

package/dist/jsenv_navi.js

@@ -37105,6 +37105,12 @@ 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, 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
  * has a rectangle where it WILL be, not where it is seen, and a press handed to
@@ -38067,6 +38073,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
@@ -40440,7 +40461,8 @@ const css$16 = /* css */`.navi_route_travel {
  * root's name is dropped for that time (`view-transition-name: none`), so what
  * stands around the box — a tab row beside it — stays live and answers a press
  * mid-travel. The application's own rule for the root applies again the moment
- * the travel is over.
+ * the travel is over. What stands out of a `FixedBar` is the exception, when it
+ * asks to stay over the pages (see `data-navi-fixed-bar-overhang` there).
  */
 const RouteTravel = ({
   routes: routesProp,
@@ -40562,6 +40584,10 @@ const RouteTravel = ({
     // transition_destination.js).
     nameForTravel(travel.element);
     holdTransitionDestination(travel, page.route.buildUrl(page.params));
+    // The bars stay live, except what one of them has photographed on its own
+    // (see fixed_bar.jsx), which is deaf like any picture and may have asked to
+    // keep answering.
+    holdTransitionPress(travel, travel.element);
     document.documentElement.setAttribute(TRAVEL_ATTRIBUTE, direction);
     document.documentElement.setAttribute(TRAVEL_AXIS_ATTRIBUTE, axis);
     if (scrub) {
@@ -40981,6 +41007,7 @@ const RouteTravel = ({
       document.documentElement.removeAttribute(TURNED_ATTRIBUTE);
       releaseTransitionWindow(travel);
       releaseTransitionDestination(travel);
+      releaseTransitionPress(travel);
     }
   };
 
@@ -41245,11 +41272,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 => {
@@ -41274,6 +41306,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);
@@ -56457,7 +56494,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.
+ *   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
@@ -59068,6 +59107,7 @@ const css$Y = /* css */`@layer navi {
 }
 
 .navi_fixed_bar_shadow {
+  z-index: -1;
   border-radius: inherit;
   box-shadow: var(--navi-fixed-bar-shadow);
   pointer-events: none;
@@ -59096,13 +59136,13 @@ const css$Y = /* css */`@layer navi {
 }
 
 @supports (view-transition-name: match-element) {
-  :root[data-navi-route-travel] .navi_fixed_bar_shadow {
+  :root[data-navi-route-travel] .navi_fixed_bar_shadow, :root[data-navi-route-travel] [data-navi-fixed-bar-overhang] {
     view-transition-name: match-element;
-    view-transition-class: navi_fixed_bar_shadow;
+    view-transition-class: navi_fixed_bar_over_pages;
   }
 }
 
-:root[data-navi-route-travel-turned]::view-transition-group(.navi_fixed_bar_shadow) {
+:root[data-navi-route-travel-turned]::view-transition-group(.navi_fixed_bar_over_pages) {
   display: block;
 }
 `;
@@ -59159,6 +59199,13 @@ const FixedBarStyleCSSVars = {
  *   Takes no room. Prefer it to a `boxShadow` or a `filter` on the bar: those
  *   are covered by the pages while a `RouteTravel` plays, this one stays over
  *   them.
+ *
+ * A child standing out of the bar's box (a raised button, the notch around it)
+ * wears `data-navi-fixed-bar-overhang`: unmarked, the pages of a `RouteTravel`
+ * cover it wherever they have paint behind it. Marked, it stays over them, and
+ * like anything photographed it is deaf for the length of the travel —
+ * `pressableDuringRouteTransition` on a control inside it keeps that control
+ * answering. The rest of the bar stays live.
  */
 const FixedBar = ({
   children,
@@ -62412,7 +62459,9 @@ const COMMAND_DEFAULT_PROPS_FACTORIES = {
  *   button in a bar the two states share, standing exactly where its picture is
  *   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.
+ *   travel with the pages. 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 {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