@allxsmith/bestax-bulma 5.67.8 → 5.67.10

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

@@ -61,7 +61,8 @@ export interface DataTableProps<TRow> extends DataTableStateOptions<TRow>, Omit<
     /**
      * Shows a page of skeleton rows under the header in place of the rows,
      * and marks the table busy. For data on its way, as from a server with
-     * `manual`.
+     * `manual`. A skeleton row is as tall as a row of one line of text, so rows
+     * of text replace it without the table changing height.
      */
     loading?: boolean;
     /**

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

@@ -85,17 +85,17 @@ export interface HoverCardProps extends Omit<React.HTMLAttributes<HTMLSpanElemen
     position?: HoverCardPosition;
     /**
      * Render the card through `Portal`, into the `portalContainer` a
-     * `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
+     * `ConfigProvider` sets, else the overlay it's in that takes its popups,
+     * such as a `Modal`, 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 an overlay, Tab reaches it
+     * only after the rest of the page or the overlay, 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.
      * @defaultValue false
      */

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

@@ -14,7 +14,12 @@ export interface PanelProps extends React.HTMLAttributes<HTMLElement>, Omit<Bulm
      * `aria-labelledby` pointing at the `id` of its `Panel.Heading`.
      */
     as?: 'nav' | 'article' | 'section' | 'aside' | 'div';
-    /** Bulma color modifier for the panel. */
+    /**
+     * Bulma color modifier for the panel. With none, the heading takes the
+     * text color, with its title in the page background's color so it reads on
+     * both schemes. On the dark scheme that title color comes from bestax's
+     * stylesheets: Bulma's CSS alone writes it white on light gray there.
+     */
     color?: 'primary' | 'link' | 'info' | 'success' | 'warning' | 'danger' | 'black' | 'dark' | 'light' | 'white';
     /** Additional CSS classes. */
     className?: string;

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

@@ -58,12 +58,12 @@ export interface PopoverProps extends Omit<React.HTMLAttributes<HTMLDivElement>,
     position?: PopoverPosition;
     /**
      * Render the panel through `Portal`, into the `portalContainer` a
-     * `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.
+     * `ConfigProvider` sets, else the overlay it's in that takes its popups,
+     * such as a `Modal`, 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/components/Sidebar.d.ts

@@ -58,7 +58,16 @@ export interface SidebarProps extends Omit<React.HTMLAttributes<HTMLElement>, 'c
     escapeClose?: boolean;
     /** Allow closing the sidebar. Default: true. */
     canCancel?: boolean;
-    /** Content to display in the sidebar. */
+    /**
+     * Content to display in the sidebar. A popup in it that portals, such as a
+     * Popover's or a date picker's panel with `appendToBody`, goes to the end
+     * of the page and renders under an open sidebar. To show it above, wrap
+     * the popup in a `ConfigProvider` whose `portalContainer` is an element of
+     * your own outside the sidebar that stacks above it, such as one with
+     * `position: relative` and a higher `z-index`. With an overlay, the
+     * sidebar's `aria-modal` still hides the popup there from screen readers
+     * that honor it.
+     */
     children?: React.ReactNode;
     /**
      * Renders inline instead of using a portal. Without it, the sidebar renders

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

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

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

@@ -97,12 +97,12 @@ interface ComboboxBaseProps extends Omit<React.HTMLAttributes<HTMLDivElement>, '
     position?: PopoverPosition;
     /**
      * Renders the menu through `Portal`, into the `portalContainer` a
-     * `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.
+     * `ConfigProvider` sets, else the overlay it's in that takes its popups,
+     * such as a `Modal`, 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

@@ -135,8 +135,8 @@ export interface DateInputBaseProps extends Omit<React.InputHTMLAttributes<HTMLI
     position?: PickerPosition;
     /**
      * Render the popover through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
-     * in, else `document.body`.
+     * `ConfigProvider` sets, else the overlay it's in that takes its popups,
+     * such as a `Modal`, else `document.body`.
      */
     appendToBody?: boolean;
     /**

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

@@ -120,8 +120,8 @@ export interface DateRangeInputBaseProps extends Omit<React.HTMLAttributes<HTMLD
     position?: PickerPosition;
     /**
      * Render the popover through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
-     * in, else `document.body`.
+     * `ConfigProvider` sets, else the overlay it's in that takes its popups,
+     * such as a `Modal`, else `document.body`.
      */
     appendToBody?: boolean;
     /**

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

@@ -111,8 +111,8 @@ export interface DateTimeInputBaseProps extends Omit<React.InputHTMLAttributes<H
     position?: PickerPosition;
     /**
      * Render the popover through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
-     * in, else `document.body`.
+     * `ConfigProvider` sets, else the overlay it's in that takes its popups,
+     * such as a `Modal`, else `document.body`.
      */
     appendToBody?: boolean;
     /**

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

@@ -86,8 +86,8 @@ export interface TimeInputBaseProps extends Omit<React.InputHTMLAttributes<HTMLI
     position?: PickerPosition;
     /**
      * Render the popover through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
-     * in, else `document.body`. On a narrow screen
+     * `ConfigProvider` sets, else the overlay it's in that takes its popups,
+     * such as a `Modal`, 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`, else the `Modal`, `Dialog` or `Command.Dialog` it's in, else `document.body`. */
+    /** Renders the panel through a portal, into a `ConfigProvider`'s `portalContainer`, else the overlay it's in that takes its popups, such as a `Modal`, else `document.body`. */
     appendToBody?: boolean;
     /** The visible and accessible strings, in your app's language. */
     labels?: TreeSelectLabels;

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

@@ -36,11 +36,15 @@ export interface ConfigProviderProps {
      * 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`, 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.
+     * opened inside an overlay that takes its popups. A `Modal`, a `Dialog`
+     * and a `Command.Dialog` do, so screen readers that honor their
+     * `aria-modal` reach the popup, and so does AppFrame's nav while it's a
+     * drawer, so the popup shows above it. A `Sidebar` doesn't, so Popover's
+     * or a picker's panel opened in an open one renders under it. Set, it
+     * takes those popups too, which is how one in a `Sidebar` shows above it:
+     * point it at an element of your own outside the sidebar that stacks above
+     * it. 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/portal.d.ts

@@ -35,15 +35,19 @@ export declare function usePortalContainer(): (container?: string | HTMLElement)
  * 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.
+ * reader that honors it hides everything outside that element. AppFrame's
+ * nav does too while it's a drawer, which draws over the page, so its popups
+ * show above it. The nearest one wins, so a Dialog's own box wins over the
+ * Modal it renders. An `undefined` node leaves the scope around it in place,
+ * for a part that only takes its popups some of the time, so its content
+ * keeps one tree either way.
  *
  * @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;
+    node: HTMLElement | null | undefined;
     children?: React.ReactNode;
 }): React.JSX.Element;
 /**

package/dist/types/layout/AppFrame.d.ts

@@ -118,7 +118,11 @@ export interface AppFrameNavProps extends Omit<React.HTMLAttributes<HTMLElement>
      * Usually a `Menu`. A nav taller than the window scrolls on its own. With
      * `overlay`, the rest of the frame is inert while the drawer is open, so an
      * overlay opened from the drawer, such as a `Modal`, goes inside the nav or
-     * renders outside the frame (Modal's `portal`).
+     * renders outside the frame (Modal's `portal`). While the nav is a drawer,
+     * a popup opened in it, such as a Popover's `appendToBody` panel, portals
+     * into the nav, so it shows above the drawer, unless a `ConfigProvider`
+     * sets a `portalContainer`. In the column it portals to the end of the
+     * page, as it does anywhere else.
      */
     children?: React.ReactNode;
     /**

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

@@ -61,7 +61,8 @@ export interface DataTableProps<TRow> extends DataTableStateOptions<TRow>, Omit<
     /**
      * Shows a page of skeleton rows under the header in place of the rows,
      * and marks the table busy. For data on its way, as from a server with
-     * `manual`.
+     * `manual`. A skeleton row is as tall as a row of one line of text, so rows
+     * of text replace it without the table changing height.
      */
     loading?: boolean;
     /**

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

@@ -85,17 +85,17 @@ export interface HoverCardProps extends Omit<React.HTMLAttributes<HTMLSpanElemen
     position?: HoverCardPosition;
     /**
      * Render the card through `Portal`, into the `portalContainer` a
-     * `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
+     * `ConfigProvider` sets, else the overlay it's in that takes its popups,
+     * such as a `Modal`, 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 an overlay, Tab reaches it
+     * only after the rest of the page or the overlay, 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.
      * @defaultValue false
      */

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

@@ -14,7 +14,12 @@ export interface PanelProps extends React.HTMLAttributes<HTMLElement>, Omit<Bulm
      * `aria-labelledby` pointing at the `id` of its `Panel.Heading`.
      */
     as?: 'nav' | 'article' | 'section' | 'aside' | 'div';
-    /** Bulma color modifier for the panel. */
+    /**
+     * Bulma color modifier for the panel. With none, the heading takes the
+     * text color, with its title in the page background's color so it reads on
+     * both schemes. On the dark scheme that title color comes from bestax's
+     * stylesheets: Bulma's CSS alone writes it white on light gray there.
+     */
     color?: 'primary' | 'link' | 'info' | 'success' | 'warning' | 'danger' | 'black' | 'dark' | 'light' | 'white';
     /** Additional CSS classes. */
     className?: string;

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

@@ -58,12 +58,12 @@ export interface PopoverProps extends Omit<React.HTMLAttributes<HTMLDivElement>,
     position?: PopoverPosition;
     /**
      * Render the panel through `Portal`, into the `portalContainer` a
-     * `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.
+     * `ConfigProvider` sets, else the overlay it's in that takes its popups,
+     * such as a `Modal`, 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/components/Sidebar.d.ts

@@ -58,7 +58,16 @@ export interface SidebarProps extends Omit<React.HTMLAttributes<HTMLElement>, 'c
     escapeClose?: boolean;
     /** Allow closing the sidebar. Default: true. */
     canCancel?: boolean;
-    /** Content to display in the sidebar. */
+    /**
+     * Content to display in the sidebar. A popup in it that portals, such as a
+     * Popover's or a date picker's panel with `appendToBody`, goes to the end
+     * of the page and renders under an open sidebar. To show it above, wrap
+     * the popup in a `ConfigProvider` whose `portalContainer` is an element of
+     * your own outside the sidebar that stacks above it, such as one with
+     * `position: relative` and a higher `z-index`. With an overlay, the
+     * sidebar's `aria-modal` still hides the popup there from screen readers
+     * that honor it.
+     */
     children?: React.ReactNode;
     /**
      * Renders inline instead of using a portal. Without it, the sidebar renders

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

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

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

@@ -97,12 +97,12 @@ interface ComboboxBaseProps extends Omit<React.HTMLAttributes<HTMLDivElement>, '
     position?: PopoverPosition;
     /**
      * Renders the menu through `Portal`, into the `portalContainer` a
-     * `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.
+     * `ConfigProvider` sets, else the overlay it's in that takes its popups,
+     * such as a `Modal`, 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

@@ -135,8 +135,8 @@ export interface DateInputBaseProps extends Omit<React.InputHTMLAttributes<HTMLI
     position?: PickerPosition;
     /**
      * Render the popover through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
-     * in, else `document.body`.
+     * `ConfigProvider` sets, else the overlay it's in that takes its popups,
+     * such as a `Modal`, else `document.body`.
      */
     appendToBody?: boolean;
     /**

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

@@ -120,8 +120,8 @@ export interface DateRangeInputBaseProps extends Omit<React.HTMLAttributes<HTMLD
     position?: PickerPosition;
     /**
      * Render the popover through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
-     * in, else `document.body`.
+     * `ConfigProvider` sets, else the overlay it's in that takes its popups,
+     * such as a `Modal`, else `document.body`.
      */
     appendToBody?: boolean;
     /**

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

@@ -111,8 +111,8 @@ export interface DateTimeInputBaseProps extends Omit<React.InputHTMLAttributes<H
     position?: PickerPosition;
     /**
      * Render the popover through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
-     * in, else `document.body`.
+     * `ConfigProvider` sets, else the overlay it's in that takes its popups,
+     * such as a `Modal`, else `document.body`.
      */
     appendToBody?: boolean;
     /**

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

@@ -86,8 +86,8 @@ export interface TimeInputBaseProps extends Omit<React.InputHTMLAttributes<HTMLI
     position?: PickerPosition;
     /**
      * Render the popover through a portal, into the `portalContainer` a
-     * `ConfigProvider` sets, else the `Modal`, `Dialog` or `Command.Dialog` it's
-     * in, else `document.body`. On a narrow screen
+     * `ConfigProvider` sets, else the overlay it's in that takes its popups,
+     * such as a `Modal`, 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`, else the `Modal`, `Dialog` or `Command.Dialog` it's in, else `document.body`. */
+    /** Renders the panel through a portal, into a `ConfigProvider`'s `portalContainer`, else the overlay it's in that takes its popups, such as a `Modal`, 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

@@ -36,11 +36,15 @@ export interface ConfigProviderProps {
      * 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`, 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.
+     * opened inside an overlay that takes its popups. A `Modal`, a `Dialog`
+     * and a `Command.Dialog` do, so screen readers that honor their
+     * `aria-modal` reach the popup, and so does AppFrame's nav while it's a
+     * drawer, so the popup shows above it. A `Sidebar` doesn't, so Popover's
+     * or a picker's panel opened in an open one renders under it. Set, it
+     * takes those popups too, which is how one in a `Sidebar` shows above it:
+     * point it at an element of your own outside the sidebar that stacks above
+     * it. 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/portal.d.ts

@@ -35,15 +35,19 @@ export declare function usePortalContainer(): (container?: string | HTMLElement)
  * 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.
+ * reader that honors it hides everything outside that element. AppFrame's
+ * nav does too while it's a drawer, which draws over the page, so its popups
+ * show above it. The nearest one wins, so a Dialog's own box wins over the
+ * Modal it renders. An `undefined` node leaves the scope around it in place,
+ * for a part that only takes its popups some of the time, so its content
+ * keeps one tree either way.
  *
  * @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;
+    node: HTMLElement | null | undefined;
     children?: React.ReactNode;
 }): React.JSX.Element;
 /**

package/dist/types-cjs/layout/AppFrame.d.ts

@@ -118,7 +118,11 @@ export interface AppFrameNavProps extends Omit<React.HTMLAttributes<HTMLElement>
      * Usually a `Menu`. A nav taller than the window scrolls on its own. With
      * `overlay`, the rest of the frame is inert while the drawer is open, so an
      * overlay opened from the drawer, such as a `Modal`, goes inside the nav or
-     * renders outside the frame (Modal's `portal`).
+     * renders outside the frame (Modal's `portal`). While the nav is a drawer,
+     * a popup opened in it, such as a Popover's `appendToBody` panel, portals
+     * into the nav, so it shows above the drawer, unless a `ConfigProvider`
+     * sets a `portalContainer`. In the column it portals to the end of the
+     * page, as it does anywhere else.
      */
     children?: React.ReactNode;
     /**