@jsenv/navi 0.29.312 → 0.29.315

package/dist/dev/jsenv_navi.js

@@ -41353,8 +41353,6 @@ time.navi_text {
 }
 
 .navi_text {
-  position: relative;
-
   &[data-capitalize] {
     &:first-letter, & .navi_text_sizer_placeholder:first-letter, & .navi_text_sizer_overlay:first-letter {
       text-transform: uppercase;
@@ -41388,6 +41386,7 @@ time.navi_text {
   &[data-skeleton] {
     visibility: hidden;
     max-width: 100%;
+    position: relative;
 
     & .navi_text_skeleton_children_placeholder {
       width: 100%;
@@ -41470,6 +41469,7 @@ time.navi_text {
 
 .navi_text[data-contains-absolute-child] {
   display: inline-block;
+  position: relative;
 }
 
 .navi_text[data-bold] {
@@ -42464,8 +42464,6 @@ const css$Y = /* css */`@layer navi {
   }
 
   &[aria-selected] {
-    position: relative;
-
     & input[type="checkbox"] {
       opacity: 0;
       position: absolute;
@@ -42479,7 +42477,16 @@ const css$Y = /* css */`@layer navi {
 
   &[data-focus], &[data-focus-visible] {
     z-index: 1;
-    position: relative;
+  }
+
+  &[data-stretch] {
+    position: static;
+
+    &:after {
+      content: "";
+      position: absolute;
+      inset: 0;
+    }
   }
 
   &[data-readonly] > * {
@@ -42706,6 +42713,15 @@ Object.assign(PSEUDO_CLASSES, {
  * @param {boolean} [props.revealOnInteraction] - Hide the link until its
  *   container is hovered/focused (`data-reveal-on-interaction`), floating it
  *   out of flow — the "#" anchor-on-hover pattern (e.g. inside a `Title`).
+ * @param {boolean} [props.stretch] - The press area is the nearest positioned
+ *   ancestor, not the link's own box (`data-stretch`): a row that leads
+ *   somewhere as a whole while only its name is the link — a button next to the
+ *   name cannot live inside an `<a>`. The ancestor to cover says so itself
+ *   (`<List.Item relative>`, `<Box relative>`), and nothing in between may be
+ *   positioned; navi's `Text` is not. A control in the row that keeps its own
+ *   press sits above the area when it is positioned and comes after the link
+ *   (navi's `Button` is positioned); one written before the link is raised
+ *   with a `z-index`. The link is never positioned itself, in any state.
  * @param {boolean} [props.hrefFallback] - Use `href` as the visible text when
  *   no children are given; defaults to `true` unless `anchor`.
  * @param {string|{type?: string, duration?: number|string, direction?: "forward"|"back"}} [props.routeTransition] -
@@ -42850,6 +42866,7 @@ const LinkPlain = props => {
     startIcon,
     endIcon,
     revealOnInteraction = false,
+    stretch,
     hrefFallback = !anchor,
     routeTransition,
     pressableDuringRouteTransition,
@@ -43023,6 +43040,7 @@ const LinkPlain = props => {
     anchor: undefined,
     slide: undefined,
     revealOnInteraction: undefined,
+    stretch: undefined,
     variant: undefined,
     current: undefined,
     currentExcept: undefined,
@@ -43113,6 +43131,7 @@ const LinkPlain = props => {
     "data-anchor": anchor ? "" : undefined,
     "data-interactive": onClick || props.command || props.action ? "" : undefined,
     "data-reveal-on-interaction": revealOnInteraction ? "" : undefined,
+    "data-stretch": stretch ? "" : undefined,
     baseClassName: "navi_link",
     styleCSSVars: LinkStyleCSSVars,
     pseudoClasses: LinkPseudoClasses,
@@ -54315,8 +54334,8 @@ const Form = props => {
   // second's opening tag, so the inner fields would silently belong to the
   // outer form. Rather than forbidding the shape (a form inside a picker inside
   // a form is a legitimate thing to want), a form that finds itself inside one
-  // is a different component: same group, no <form> element and none of the
-  // browser machinery that comes with it.
+  // is a different component: a group of its own, no <form> element and none of
+  // the browser machinery that comes with it (see FormNested).
   const isNested = Boolean(useContext(FormContext));
   return isNested ? jsx(FormNested, {
     ...props
@@ -54446,13 +54465,26 @@ const FormControl = props => {
 // event to intercept and no requestSubmit() to go through, so it is driven the
 // way every other group is — a command, or an action requested on it. method
 // belongs to the browser's own submission, so it means nothing here either.
+//
+// And it owns what it holds: `standalone`, unconditionally. A <Form> is a
+// question with a send of its own, so its fields answer to it and to nothing
+// above it — they are not in the outer form's value, not in its "changed", and
+// not in the constraints it checks before sending. That last one is what a
+// caller feels: a required field in a popup nobody opened would otherwise
+// refuse the outer submit, pointing at something the screen is not even
+// showing. A cluster of fields that IS part of the value around it is a
+// <ControlGroup>, which is the shape without the send (see
+// docs/control_object.md).
 const FormNested = props => {
   const {
     formRootProps,
     formProps,
     onnavi_action_end,
     inside
-  } = useFormGroup(props);
+  } = useFormGroup({
+    ...props,
+    standalone: true
+  });
   return jsx(Box, {
     ...formRootProps,
     ...formProps,
@@ -59494,6 +59526,18 @@ const css$E = /* css */`
     --x-corner-bottom-right-radius: initial;
     --x-corner-bottom-left-radius: initial;
 
+    /* Sizing is per dialog: the anchor box (sizeFromAnchor) and the
+       minWidth/maxWidth/minHeight/maxHeight props are written inline on THIS
+       element, and an inline declaration wins over these resets. Without
+       them, a dialog nested in another dialog would inherit its parent's
+       inline values and open at the parent's size. */
+    --anchor-width: initial;
+    --anchor-height: initial;
+    --dialog-min-width: initial;
+    --dialog-max-width: initial;
+    --dialog-min-height: initial;
+    --dialog-max-height: initial;
+
     /* Computed once, reused by both max-width itself and min-width's own
        clamp below (see its comment for why) — avoids repeating the same
        min(..., ...) expression twice. */
@@ -61403,6 +61447,21 @@ const css$D = /* css */`
     --x-corner-bottom-right-radius: initial;
     --x-corner-bottom-left-radius: initial;
 
+    /* Sizing is per popover: the anchor box and the
+       minWidth/maxWidth/minHeight/maxHeight props are written inline on THIS
+       element, and an inline declaration wins over these resets. Without
+       them, a popover nested in another popup (or opened without an anchor
+       inside one sized from its own) would inherit the outer inline values
+       and open at the outer size. */
+    --anchor-width: initial;
+    --anchor-height: initial;
+    --anchor-inner-width: initial;
+    --anchor-inner-height: initial;
+    --popover-min-width: initial;
+    --popover-max-width: initial;
+    --popover-min-height: initial;
+    --popover-max-height: initial;
+
     --x-popover-max-width: min(
       var(--popover-max-width, var(--popover-maxmax-width)),
       var(--container-position-remaining-width, var(--popover-maxmax-width)),
@@ -71611,9 +71670,11 @@ const PickerText = props => {
 };
 
 // The popup holds a group of named controls — a `<ControlGroup>`, or a `<Form>`
-// when that group is a question with a send of its own — and this picker's
-// value is the object that group aggregates. The popup itself holds nothing: it
-// is a surface (see dialog.jsx), so there is nothing to tell it about the shape.
+// when that group is a question with a send of its own and the picker is not
+// itself inside a form (a form in a form answers for itself, see form.jsx) —
+// and this picker's value is the object that group aggregates. The popup itself
+// holds nothing: it is a surface (see dialog.jsx), so there is nothing to tell
+// it about the shape.
 const PickerObject = props => {
   const Next = useNextResolver();
   return jsx(Next, {