@allxsmith/bestax-bulma 5.67.2 → 5.67.3

package/dist/types/components/HoverCard.d.ts

@@ -81,14 +81,15 @@ export interface HoverCardProps extends Omit<React.HTMLAttributes<HTMLSpanElemen
     position?: HoverCardPosition;
     /**
      * Render the card through `Portal`, into the `portalContainer` a
-     * `ConfigProvider` sets, `document.body` by default, fixed to the viewport,
-     * so an ancestor's `overflow`, `transform` or stacking context can't clip
-     * it. A trigger in running text needs it too, since the card's block
-     * content can't sit inside a `<p>`. The card then shows from the commit
-     * after hydration, never in server markup, and it sits in the Tab order
-     * where its container is. At the end of `<body>`, the default, Tab reaches
-     * it only after the rest of the page, and focus leaving the trigger on the
-     * way closes it, so keyboard users can open it, read it and close it with
+     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog`
+     * it's in, else `document.body`, fixed to the viewport, so an ancestor's
+     * `overflow`, `transform` or stacking context can't clip it. A trigger in
+     * running text needs it too, since the card's block content can't sit
+     * inside a `<p>`. The card then shows from the commit after hydration,
+     * never in server markup, and it sits in the Tab order where its container
+     * is. At the end of `<body>` or of a dialog, Tab reaches it only after the
+     * rest of the page or the dialog, and focus leaving the trigger on the way
+     * closes it, so keyboard users can open it, read it and close it with
      * Escape, and whatever it links to has to be reachable from the page as
      * well. Theming variables set on an ancestor of the trigger reach it only
      * when its container is inside that ancestor.

package/dist/types/components/Popover.d.ts

@@ -58,11 +58,12 @@ export interface PopoverProps extends Omit<React.HTMLAttributes<HTMLDivElement>,
     position?: PopoverPosition;
     /**
      * Render the panel through `Portal`, into the `portalContainer` a
-     * `ConfigProvider` sets, `document.body` by default, fixed to the viewport,
-     * so an ancestor's `overflow`, `transform` or stacking context can't clip
-     * it. The panel then shows from the commit after hydration, never in server
-     * markup. Theming variables set on an ancestor of the trigger reach it only
-     * when its container is inside that ancestor.
+     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog`
+     * it's in, else `document.body`, fixed to the viewport, so an ancestor's
+     * `overflow`, `transform` or stacking context can't clip it. The panel
+     * then shows from the commit after hydration, never in server markup.
+     * Theming variables set on an ancestor of the trigger reach it only when
+     * its container is inside that ancestor.
      * @defaultValue false
      */
     appendToBody?: boolean;

package/dist/types/form/ColorInputBase.d.ts

@@ -73,7 +73,8 @@ export interface ColorInputBaseProps extends Omit<React.InputHTMLAttributes<HTML
     position?: PickerPosition;
     /**
      * Renders the panel through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, `document.body` by default.
+     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
+     * in, else `document.body`.
      */
     appendToBody?: boolean;
     /** Bulma color modifier for the field. */

package/dist/types/form/Combobox.d.ts

@@ -94,13 +94,12 @@ interface ComboboxBaseProps extends Omit<React.HTMLAttributes<HTMLDivElement>, '
     position?: PopoverPosition;
     /**
      * Renders the menu through `Portal`, into the `portalContainer` a
-     * `ConfigProvider` sets, `document.body` by default, fixed to the viewport
-     * at the field, so a container that clips its overflow can't cut it off.
-     * It then shows from the commit after hydration, never in server markup.
-     * Theming variables set on an ancestor reach it only when the portal's
-     * container is inside that ancestor, as with Popover. In a `Modal`, point
-     * `portalContainer` inside the modal, so the list stays in the dialog for
-     * assistive tech.
+     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog`
+     * it's in, else `document.body`, fixed to the viewport at the field, so a
+     * container that clips its overflow can't cut it off. It then shows from
+     * the commit after hydration, never in server markup. Theming variables set
+     * on an ancestor reach it only when the portal's container is inside that
+     * ancestor, as with Popover.
      * @defaultValue false
      */
     appendToBody?: boolean;

package/dist/types/form/DateInputBase.d.ts

@@ -128,7 +128,8 @@ export interface DateInputBaseProps extends Omit<React.InputHTMLAttributes<HTMLI
     position?: PickerPosition;
     /**
      * Render the popover through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, `document.body` by default.
+     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
+     * in, else `document.body`.
      */
     appendToBody?: boolean;
     /**

package/dist/types/form/DateRangeInputBase.d.ts

@@ -113,7 +113,8 @@ export interface DateRangeInputBaseProps extends Omit<React.HTMLAttributes<HTMLD
     position?: PickerPosition;
     /**
      * Render the popover through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, `document.body` by default.
+     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
+     * in, else `document.body`.
      */
     appendToBody?: boolean;
     /**

package/dist/types/form/DateTimeInputBase.d.ts

@@ -101,7 +101,8 @@ export interface DateTimeInputBaseProps extends Omit<React.InputHTMLAttributes<H
     position?: PickerPosition;
     /**
      * Render the popover through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, `document.body` by default.
+     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
+     * in, else `document.body`.
      */
     appendToBody?: boolean;
     /**

package/dist/types/form/TimeInputBase.d.ts

@@ -75,7 +75,8 @@ export interface TimeInputBaseProps extends Omit<React.InputHTMLAttributes<HTMLI
     position?: PickerPosition;
     /**
      * Render the popover through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, `document.body` by default. On a narrow screen
+     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
+     * in, else `document.body`. On a narrow screen
      * an in-place popover spans the bottom of the viewport, while a portaled
      * one stays on its `position` corner.
      */

package/dist/types/form/TreeSelect.d.ts

@@ -164,7 +164,7 @@ interface TreeSelectBaseProps extends Omit<React.HTMLAttributes<HTMLDivElement>,
      * @defaultValue 'bottom-left'
      */
     position?: PickerPosition;
-    /** Renders the panel through a portal, into a `ConfigProvider`'s `portalContainer`, `document.body` by default. */
+    /** Renders the panel through a portal, into a `ConfigProvider`'s `portalContainer`, else the `Modal`, `Dialog` or `Command.Dialog` it's in, else `document.body`. */
     appendToBody?: boolean;
     /** The visible and accessible strings, in your app's language. */
     labels?: TreeSelectLabels;

package/dist/types/helpers/Config.d.ts

@@ -35,9 +35,12 @@ export interface ConfigProviderProps {
      * portal, such as Popover's `appendToBody` panel, a `Modal` with `portal`
      * set to `true`, or a `Toast`. An element, or a `document.querySelector`
      * selector. Unset, or a selector that matches nothing, that content goes to
-     * `document.body`. A target a component is given, such as a `Toast`'s
-     * `container`, still wins, and nothing portals that would otherwise render
-     * in place.
+     * `document.body`, except a popup, such as Popover's panel or a picker's,
+     * opened inside a `Modal`, `Dialog` or `Command.Dialog`: that goes into the
+     * dialog, where screen readers that honor its `aria-modal` reach it. Set,
+     * it takes those popups too. A target a component is given, such as a
+     * `Toast`'s `container`, still wins, and nothing portals that would
+     * otherwise render in place.
      *
      * The overlays and panels this moves are `position: fixed`, so pick an
      * element with no ancestor that has a `transform`, `filter`,

package/dist/types/helpers/elementType.d.ts

@@ -0,0 +1,20 @@
+import React from 'react';
+/**
+ * The component an element renders, read through a lazy type.
+ *
+ * A client component written in a React Server Component reaches the client
+ * as a client reference, whose element type is lazy rather than the
+ * component's own function, so `child.type === Part` is never true there
+ * (#1500). This resolves a lazy type the way React does when it renders one:
+ * a module that has loaded gives its component, one still loading throws, so
+ * the caller suspends at the boundary the element itself would have, and one
+ * that failed throws its error. A lazy type without those fields comes back
+ * as it is, so a part goes unrecognized, which is what happened before.
+ */
+export declare function elementType(element: React.ReactElement): unknown;
+/**
+ * Whether `node` is an element of one of `types`, including one written in a
+ * Server Component. A parent tells its parts apart with this, never by
+ * comparing `child.type`.
+ */
+export declare function isElementOf<P = unknown>(node: React.ReactNode, ...types: readonly unknown[]): node is React.ReactElement<P>;

package/dist/types/helpers/portal.d.ts

@@ -30,6 +30,39 @@ export declare function resolvePortalContainer(container?: string | HTMLElement)
  * returns the DOM node to portal into.
  */
 export declare function usePortalContainer(): (container?: string | HTMLElement) => HTMLElement;
+/**
+ * INTERNAL, deliberately not exported from `src/index.ts`. Makes `node` where
+ * the popups inside it portal, unless a `ConfigProvider` sets a
+ * `portalContainer`. Modal, Dialog and Command.Dialog wrap their content in
+ * it, each with the element that carries their `aria-modal`, since a screen
+ * reader that honors it hides everything outside that element. The nearest
+ * one wins, so a Dialog's own box wins over the Modal it renders.
+ *
+ * @function PortalScope
+ * @param props - `node`, the element popups portal into, and `children`.
+ * @returns The children, inside the scope.
+ */
+export declare function PortalScope({ node, children, }: {
+    node: HTMLElement | null;
+    children?: React.ReactNode;
+}): React.JSX.Element;
+/**
+ * INTERNAL. Where a popup portals, a panel a component opens against
+ * something on the page, such as Popover's: the `portalContainer` a
+ * `ConfigProvider` sets, else the overlay it's in (see `PortalScope`), else
+ * `undefined`, which `resolvePortalContainer` reads as `document.body`.
+ *
+ * The overlay's element only exists once it has mounted, so a popup open as
+ * the overlay first renders mounts in `document.body`, and moves into the
+ * overlay in the update that follows, before the browser paints. Moving
+ * remounts it, as any change of portal target does. It isn't held back
+ * instead, because the popups measure their panel against the trigger as
+ * they open, and a panel that isn't there yet is never placed.
+ *
+ * @function usePopupContainer
+ * @returns The popup's container, `undefined` for `document.body`.
+ */
+export declare function usePopupContainer(): string | HTMLElement | undefined;
 /**
  * What a component that takes Modal's `portal` prop does with it now. See
  * `usePortalProp`.
@@ -151,3 +184,14 @@ export interface PortalProps {
  * </Portal>
  */
 export declare function Portal({ children, container, disabled }: PortalProps): React.JSX.Element | null;
+/**
+ * INTERNAL. `Portal` for a popup, into the container `usePopupContainer`
+ * names, so a popup opened inside a Modal, Dialog or Command.Dialog stays
+ * inside it. `disabled` renders the children in place, as `Portal`'s does.
+ *
+ * @function PopupPortal
+ * @param props - The children, and `disabled`.
+ * @returns The portal, the children in place when `disabled`, or nothing
+ * before hydration.
+ */
+export declare function PopupPortal({ children, disabled, }: Omit<PortalProps, 'container'>): React.JSX.Element;

package/dist/types/helpers/useAnchoredPosition.d.ts

@@ -85,7 +85,9 @@ export declare function marginGap(panel: HTMLElement): number;
  * anchor changes size, so a fixed panel follows its anchor and its own
  * content. Those measure once in the next frame, however many arrive before
  * it. With `followContent` it also measures after each render. A
- * measurement that changes nothing doesn't render again.
+ * measurement that changes nothing doesn't render again. A panel that's
+ * replaced while it's open, as a portal moving to another target replaces
+ * it, is watched from the next measurement on.
  *
  * The first measurement happens in a layout effect, so the panel is placed
  * before it paints. It needs both elements on the page while `active` is

package/dist/types/helpers/withSubComponents.d.ts

@@ -4,7 +4,7 @@
  *
  * Internal helper — it MUST mutate and return the same function object
  * (`Object.assign`), never wrap the base in a new function: identity checks
- * like `child.type === ModalCard` (Modal) and Field's displayName-based
+ * like `isElementOf(child, ModalCard)` (Modal) and Field's displayName-based
  * child detection rely on the attached component being the same object as
  * the separately exported one.
  *

package/dist/types-cjs/components/HoverCard.d.ts

@@ -81,14 +81,15 @@ export interface HoverCardProps extends Omit<React.HTMLAttributes<HTMLSpanElemen
     position?: HoverCardPosition;
     /**
      * Render the card through `Portal`, into the `portalContainer` a
-     * `ConfigProvider` sets, `document.body` by default, fixed to the viewport,
-     * so an ancestor's `overflow`, `transform` or stacking context can't clip
-     * it. A trigger in running text needs it too, since the card's block
-     * content can't sit inside a `<p>`. The card then shows from the commit
-     * after hydration, never in server markup, and it sits in the Tab order
-     * where its container is. At the end of `<body>`, the default, Tab reaches
-     * it only after the rest of the page, and focus leaving the trigger on the
-     * way closes it, so keyboard users can open it, read it and close it with
+     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog`
+     * it's in, else `document.body`, fixed to the viewport, so an ancestor's
+     * `overflow`, `transform` or stacking context can't clip it. A trigger in
+     * running text needs it too, since the card's block content can't sit
+     * inside a `<p>`. The card then shows from the commit after hydration,
+     * never in server markup, and it sits in the Tab order where its container
+     * is. At the end of `<body>` or of a dialog, Tab reaches it only after the
+     * rest of the page or the dialog, and focus leaving the trigger on the way
+     * closes it, so keyboard users can open it, read it and close it with
      * Escape, and whatever it links to has to be reachable from the page as
      * well. Theming variables set on an ancestor of the trigger reach it only
      * when its container is inside that ancestor.

package/dist/types-cjs/components/Popover.d.ts

@@ -58,11 +58,12 @@ export interface PopoverProps extends Omit<React.HTMLAttributes<HTMLDivElement>,
     position?: PopoverPosition;
     /**
      * Render the panel through `Portal`, into the `portalContainer` a
-     * `ConfigProvider` sets, `document.body` by default, fixed to the viewport,
-     * so an ancestor's `overflow`, `transform` or stacking context can't clip
-     * it. The panel then shows from the commit after hydration, never in server
-     * markup. Theming variables set on an ancestor of the trigger reach it only
-     * when its container is inside that ancestor.
+     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog`
+     * it's in, else `document.body`, fixed to the viewport, so an ancestor's
+     * `overflow`, `transform` or stacking context can't clip it. The panel
+     * then shows from the commit after hydration, never in server markup.
+     * Theming variables set on an ancestor of the trigger reach it only when
+     * its container is inside that ancestor.
      * @defaultValue false
      */
     appendToBody?: boolean;

package/dist/types-cjs/form/ColorInputBase.d.ts

@@ -73,7 +73,8 @@ export interface ColorInputBaseProps extends Omit<React.InputHTMLAttributes<HTML
     position?: PickerPosition;
     /**
      * Renders the panel through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, `document.body` by default.
+     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
+     * in, else `document.body`.
      */
     appendToBody?: boolean;
     /** Bulma color modifier for the field. */

package/dist/types-cjs/form/Combobox.d.ts

@@ -94,13 +94,12 @@ interface ComboboxBaseProps extends Omit<React.HTMLAttributes<HTMLDivElement>, '
     position?: PopoverPosition;
     /**
      * Renders the menu through `Portal`, into the `portalContainer` a
-     * `ConfigProvider` sets, `document.body` by default, fixed to the viewport
-     * at the field, so a container that clips its overflow can't cut it off.
-     * It then shows from the commit after hydration, never in server markup.
-     * Theming variables set on an ancestor reach it only when the portal's
-     * container is inside that ancestor, as with Popover. In a `Modal`, point
-     * `portalContainer` inside the modal, so the list stays in the dialog for
-     * assistive tech.
+     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog`
+     * it's in, else `document.body`, fixed to the viewport at the field, so a
+     * container that clips its overflow can't cut it off. It then shows from
+     * the commit after hydration, never in server markup. Theming variables set
+     * on an ancestor reach it only when the portal's container is inside that
+     * ancestor, as with Popover.
      * @defaultValue false
      */
     appendToBody?: boolean;

package/dist/types-cjs/form/DateInputBase.d.ts

@@ -128,7 +128,8 @@ export interface DateInputBaseProps extends Omit<React.InputHTMLAttributes<HTMLI
     position?: PickerPosition;
     /**
      * Render the popover through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, `document.body` by default.
+     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
+     * in, else `document.body`.
      */
     appendToBody?: boolean;
     /**

package/dist/types-cjs/form/DateRangeInputBase.d.ts

@@ -113,7 +113,8 @@ export interface DateRangeInputBaseProps extends Omit<React.HTMLAttributes<HTMLD
     position?: PickerPosition;
     /**
      * Render the popover through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, `document.body` by default.
+     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
+     * in, else `document.body`.
      */
     appendToBody?: boolean;
     /**

package/dist/types-cjs/form/DateTimeInputBase.d.ts

@@ -101,7 +101,8 @@ export interface DateTimeInputBaseProps extends Omit<React.InputHTMLAttributes<H
     position?: PickerPosition;
     /**
      * Render the popover through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, `document.body` by default.
+     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
+     * in, else `document.body`.
      */
     appendToBody?: boolean;
     /**

package/dist/types-cjs/form/TimeInputBase.d.ts

@@ -75,7 +75,8 @@ export interface TimeInputBaseProps extends Omit<React.InputHTMLAttributes<HTMLI
     position?: PickerPosition;
     /**
      * Render the popover through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, `document.body` by default. On a narrow screen
+     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
+     * in, else `document.body`. On a narrow screen
      * an in-place popover spans the bottom of the viewport, while a portaled
      * one stays on its `position` corner.
      */

package/dist/types-cjs/form/TreeSelect.d.ts

@@ -164,7 +164,7 @@ interface TreeSelectBaseProps extends Omit<React.HTMLAttributes<HTMLDivElement>,
      * @defaultValue 'bottom-left'
      */
     position?: PickerPosition;
-    /** Renders the panel through a portal, into a `ConfigProvider`'s `portalContainer`, `document.body` by default. */
+    /** Renders the panel through a portal, into a `ConfigProvider`'s `portalContainer`, else the `Modal`, `Dialog` or `Command.Dialog` it's in, else `document.body`. */
     appendToBody?: boolean;
     /** The visible and accessible strings, in your app's language. */
     labels?: TreeSelectLabels;

package/dist/types-cjs/helpers/Config.d.ts

@@ -35,9 +35,12 @@ export interface ConfigProviderProps {
      * portal, such as Popover's `appendToBody` panel, a `Modal` with `portal`
      * set to `true`, or a `Toast`. An element, or a `document.querySelector`
      * selector. Unset, or a selector that matches nothing, that content goes to
-     * `document.body`. A target a component is given, such as a `Toast`'s
-     * `container`, still wins, and nothing portals that would otherwise render
-     * in place.
+     * `document.body`, except a popup, such as Popover's panel or a picker's,
+     * opened inside a `Modal`, `Dialog` or `Command.Dialog`: that goes into the
+     * dialog, where screen readers that honor its `aria-modal` reach it. Set,
+     * it takes those popups too. A target a component is given, such as a
+     * `Toast`'s `container`, still wins, and nothing portals that would
+     * otherwise render in place.
      *
      * The overlays and panels this moves are `position: fixed`, so pick an
      * element with no ancestor that has a `transform`, `filter`,

package/dist/types-cjs/helpers/elementType.d.ts

@@ -0,0 +1,20 @@
+import React from 'react';
+/**
+ * The component an element renders, read through a lazy type.
+ *
+ * A client component written in a React Server Component reaches the client
+ * as a client reference, whose element type is lazy rather than the
+ * component's own function, so `child.type === Part` is never true there
+ * (#1500). This resolves a lazy type the way React does when it renders one:
+ * a module that has loaded gives its component, one still loading throws, so
+ * the caller suspends at the boundary the element itself would have, and one
+ * that failed throws its error. A lazy type without those fields comes back
+ * as it is, so a part goes unrecognized, which is what happened before.
+ */
+export declare function elementType(element: React.ReactElement): unknown;
+/**
+ * Whether `node` is an element of one of `types`, including one written in a
+ * Server Component. A parent tells its parts apart with this, never by
+ * comparing `child.type`.
+ */
+export declare function isElementOf<P = unknown>(node: React.ReactNode, ...types: readonly unknown[]): node is React.ReactElement<P>;

package/dist/types-cjs/helpers/portal.d.ts

@@ -30,6 +30,39 @@ export declare function resolvePortalContainer(container?: string | HTMLElement)
  * returns the DOM node to portal into.
  */
 export declare function usePortalContainer(): (container?: string | HTMLElement) => HTMLElement;
+/**
+ * INTERNAL, deliberately not exported from `src/index.ts`. Makes `node` where
+ * the popups inside it portal, unless a `ConfigProvider` sets a
+ * `portalContainer`. Modal, Dialog and Command.Dialog wrap their content in
+ * it, each with the element that carries their `aria-modal`, since a screen
+ * reader that honors it hides everything outside that element. The nearest
+ * one wins, so a Dialog's own box wins over the Modal it renders.
+ *
+ * @function PortalScope
+ * @param props - `node`, the element popups portal into, and `children`.
+ * @returns The children, inside the scope.
+ */
+export declare function PortalScope({ node, children, }: {
+    node: HTMLElement | null;
+    children?: React.ReactNode;
+}): React.JSX.Element;
+/**
+ * INTERNAL. Where a popup portals, a panel a component opens against
+ * something on the page, such as Popover's: the `portalContainer` a
+ * `ConfigProvider` sets, else the overlay it's in (see `PortalScope`), else
+ * `undefined`, which `resolvePortalContainer` reads as `document.body`.
+ *
+ * The overlay's element only exists once it has mounted, so a popup open as
+ * the overlay first renders mounts in `document.body`, and moves into the
+ * overlay in the update that follows, before the browser paints. Moving
+ * remounts it, as any change of portal target does. It isn't held back
+ * instead, because the popups measure their panel against the trigger as
+ * they open, and a panel that isn't there yet is never placed.
+ *
+ * @function usePopupContainer
+ * @returns The popup's container, `undefined` for `document.body`.
+ */
+export declare function usePopupContainer(): string | HTMLElement | undefined;
 /**
  * What a component that takes Modal's `portal` prop does with it now. See
  * `usePortalProp`.
@@ -151,3 +184,14 @@ export interface PortalProps {
  * </Portal>
  */
 export declare function Portal({ children, container, disabled }: PortalProps): React.JSX.Element | null;
+/**
+ * INTERNAL. `Portal` for a popup, into the container `usePopupContainer`
+ * names, so a popup opened inside a Modal, Dialog or Command.Dialog stays
+ * inside it. `disabled` renders the children in place, as `Portal`'s does.
+ *
+ * @function PopupPortal
+ * @param props - The children, and `disabled`.
+ * @returns The portal, the children in place when `disabled`, or nothing
+ * before hydration.
+ */
+export declare function PopupPortal({ children, disabled, }: Omit<PortalProps, 'container'>): React.JSX.Element;

package/dist/types-cjs/helpers/useAnchoredPosition.d.ts

@@ -85,7 +85,9 @@ export declare function marginGap(panel: HTMLElement): number;
  * anchor changes size, so a fixed panel follows its anchor and its own
  * content. Those measure once in the next frame, however many arrive before
  * it. With `followContent` it also measures after each render. A
- * measurement that changes nothing doesn't render again.
+ * measurement that changes nothing doesn't render again. A panel that's
+ * replaced while it's open, as a portal moving to another target replaces
+ * it, is watched from the next measurement on.
  *
  * The first measurement happens in a layout effect, so the panel is placed
  * before it paints. It needs both elements on the page while `active` is

package/dist/types-cjs/helpers/withSubComponents.d.ts

@@ -4,7 +4,7 @@
  *
  * Internal helper — it MUST mutate and return the same function object
  * (`Object.assign`), never wrap the base in a new function: identity checks
- * like `child.type === ModalCard` (Modal) and Field's displayName-based
+ * like `isElementOf(child, ModalCard)` (Modal) and Field's displayName-based
  * child detection rely on the attached component being the same object as
  * the separately exported one.
  *