@sesamehr/react-design-system 2.0.0-beta.8 → 2.0.0-beta.9

package/dist/Feedback/Popover/PopoverContent.d.ts

@@ -3,11 +3,4 @@ export interface PopoverContentProps extends React.ComponentPropsWithoutRef<type
     showArrow?: boolean;
     dataTestid: string;
 }
-/**
- * PopoverContent — portalled Radix popover content with optional arrow.
- *
- * `asChild` draws it on the shared `Surface`, which is what keeps a popover
- * and a select open on the same screen from having different corners. Only the
- * padding is a popover's own.
- */
 export declare const PopoverContent: import('react').ForwardRefExoticComponent<PopoverContentProps & import('react').RefAttributes<HTMLDivElement>>;

package/dist/Feedback/Tooltip/TooltipContent.d.ts

@@ -3,5 +3,4 @@ export interface TooltipContentProps extends React.ComponentPropsWithoutRef<type
     showArrow?: boolean;
     dataTestid: string;
 }
-/** TooltipContent — portalled Radix tooltip content with optional arrow. */
 export declare const TooltipContent: import('react').ForwardRefExoticComponent<TooltipContentProps & import('react').RefAttributes<HTMLDivElement>>;

package/dist/Forms/Inputs/Combobox/ComboboxContent.d.ts

@@ -4,15 +4,4 @@ export interface ComboboxContentProps extends Omit<React.ComponentPropsWithoutRe
     sideOffset?: number;
     align?: 'start' | 'center' | 'end';
 }
-/**
- * ComboboxContent — the popover surface and the scrollable list in one.
- * `@radix-ui/react-popover` provides the portal + positioning; `cmdk`'s `Command`
- * provides item filtering. A visually-hidden `CommandInput` receives the shared
- * search string so typing in the anchored input filters the list.
- *
- * `asChild` puts the shared `Surface` where the popover content element would
- * be, and the shared viewport where cmdk's list would be, so a combobox and a
- * select are the same card with the same padding by construction rather than
- * by two stylesheets agreeing.
- */
 export declare const ComboboxContent: import('react').ForwardRefExoticComponent<ComboboxContentProps & import('react').RefAttributes<HTMLDivElement>>;

package/dist/Forms/Inputs/SearchPanel/SearchPanelList.d.ts

@@ -1,36 +1,5 @@
 import { CommandList } from 'cmdk';
 export type SearchPanelListProps = React.ComponentPropsWithoutRef<typeof CommandList>;
-/**
- * The scrolling list of groups and rows — `role="listbox"` and the rows in it —
- * on a card that floats over the page.
- *
- * **It floats, and that is the point.** In the flow it pushed everything below
- * the panel down the moment an answer landed, which is not what a dropdown does
- * and is disqualifying for a search that lives in a header. The card is
- * positioned by Radix's popper against the anchor `SearchPanel` wraps around
- * itself, so it is exactly the field's width, it flips above the field when
- * there is no room below, and it is `position: fixed` — no ancestor's
- * `overflow` can clip it.
- *
- * **No portal, and that is also the point.** Everything the keyboard is made of
- * is a relationship between this list and the field above it: cmdk gathers the
- * rows by querying the `Command` element they sit inside, `aria-activedescendant`
- * on the field points at a row's `id`, and the panel's custom properties reach
- * the rows by inheriting down the tree. A `Popover.Portal` would move the rows
- * out of `Command` entirely, and the arrows would stop finding them.
- * Popper-positioned content does not need a portal to escape the flow —
- * `position: fixed` already does — so it does not get one.
- *
- * The two auto-focus events are prevented for the same reason. A popover
- * focuses its content when it opens and hands focus back when it closes; both
- * would take focus off the search field, which is the one thing the arrow keys
- * depend on. `role="presentation"` and the blanked `aria-labelledby` finish the
- * job: the primitive believes it is a dialog, a screen reader must not, and the
- * name it points at belongs to a trigger this panel does not have. Radix
- * spreads the caller's props *after* its own `role`, so saying so here is
- * enough — the Vue port has to write the same two attributes one level further
- * down, where reka merges last.
- */
 export declare const SearchPanelList: import('react').ForwardRefExoticComponent<Omit<{
     children?: React.ReactNode;
 } & Pick<Pick<import('react').DetailedHTMLProps<import('react').HTMLAttributes<HTMLDivElement>, HTMLDivElement>, "key" | keyof import('react').HTMLAttributes<HTMLDivElement>> & {

package/dist/Forms/Inputs/Select/SelectContent.d.ts

@@ -4,14 +4,4 @@ export interface SelectContentProps extends Omit<React.ComponentPropsWithoutRef<
     sideOffset?: number;
     align?: 'start' | 'center' | 'end';
 }
-/**
- * The floating list. Always positioned against the trigger rather than over it,
- * so the popup matches the trigger's width and never covers it.
- *
- * `asChild` hands the primitive's positioning, `data-state` and `data-side` to
- * the shared `Surface`, which is the one element `Popover`, `Select`,
- * `Combobox` and `SearchPanel` may have in common. Exactly one child sits at
- * each slot position — Radix's `Slot` throws on a second, which is the whole
- * reason the arrangement is safe to read at a glance.
- */
 export declare const SelectContent: import('react').ForwardRefExoticComponent<SelectContentProps & import('react').RefAttributes<HTMLDivElement>>;