import { Tabs as Primitive } from "@base-ui/react/tabs";
export declare const Tabs: import("react").ForwardRefExoticComponent<Omit<import("@base-ui/react").TabsRootProps, "ref"> & import("react").RefAttributes<HTMLDivElement>>;
export declare const TabPanel: import("react").ForwardRefExoticComponent<Omit<import("@base-ui/react").TabsPanelProps, "ref"> & import("react").RefAttributes<HTMLDivElement>>;
type TabListLabel = {
    label: string;
    "aria-labelledby"?: undefined;
} | {
    label?: undefined;
    "aria-labelledby": string;
};
export type TabListProps = Omit<Primitive.List.Props, "aria-labelledby"> & TabListLabel & {
    /** Classes for the wrapper that owns the sideways scroll. */
    wrapperClassName?: string;
};
/**
 * The rail, and the reason this file exists.
 *
 * It scrolls sideways rather than wrapping, because a second row of tabs pushes the panel below the
 * fold on a phone. But the scroll cannot live on the rail itself: `overflow-x: auto` makes the
 * element a scroll container, a scroll container clips everything its children paint outside the
 * padding box, and a computed `overflow-x` of `auto` forces `overflow-y` from `visible` to `auto`
 * as well. A self-scrolling rail therefore crops the focus ring on all FOUR sides of whichever tab
 * the keyboard is on: top and bottom always, the left of the first tab and the right of the last.
 *
 * So the scroll goes on a wrapper, and the wrapper's padding is the room the ring needs. The
 * number is derived, not inherited: `@gusnips/tokens` draws `outline: 2px solid` at
 * `outline-offset: 2px`, so the ring paints from 2px to 4px beyond a tab's border box, and
 * `p-1` is exactly those 4px. An outline reaches FURTHER than the `ring-2` box-shadow the
 * donor had here, so the wrapper matters more now than it did there, not less.
 *
 * Naming the rail is not optional and not a comment: pass `label`, or point
 * `aria-labelledby` at a heading. A tablist with neither is announced as nothing at all.
 */
export declare function TabList({ label, className, wrapperClassName, children, ...rest }: TabListProps): import("react").JSX.Element;
export declare function Tab({ className, ...rest }: Primitive.Tab.Props): import("react").JSX.Element;
/**
 * The travelling marker under the active tab. A SEPARATE part, because the two donors disagreed
 * about whether to have one at all and both were right about their own app. Render it or do not;
 * the rail works either way.
 *
 * It must be a child of `TabList`: Base UI measures the active tab against the enclosing
 * `[role="tablist"]` and writes `--active-tab-left` / `--active-tab-width` onto this element.
 *
 * `renderBeforeHydration` is on by default because this package's apps are prerendered. With it
 * off, every prerendered page shows the rail with no marker until React arrives. It writes one
 * inline script to do that; under a strict CSP without Base UI's `CspProvider` the script is
 * blocked and the behaviour falls back to exactly what `false` would have done.
 */
export declare function TabIndicator({ className, ...rest }: Primitive.Indicator.Props): import("react").JSX.Element;
export {};
//# sourceMappingURL=tabs.d.ts.map