import "./text_disclosure.css";
import type * as React from "react";
import { Button as Base } from "@base-ui/react/button";
import { type StyleProps } from "./style_props";
import type { TextSize } from "./text";
/** No `TriggerProps`: a disclosure reveals content already on the page, never an overlay, and `onToggle`
 *  would collide with the DOM's `<details>` event name. */
export interface TextDisclosureProps extends StyleProps {
    /** Controlled, since the revealed content is the caller's. */
    expanded: boolean;
    onToggle: (expanded: boolean) => void;
    /** The noun behind it ("transcript", "3 earlier replies"); the verb is supplied, so one control keeps
     *  one vocabulary. */
    label: string;
    /** Default "sm". */
    size?: TextSize;
    /** When `label` is ambiguous among several on a page. */
    accessibilityLabel?: string;
    testID?: string;
    ref?: React.Ref<HTMLElement>;
    render?: Base.Props["render"];
}
/**
 * An in-prose disclosure: muted underlined text revealing adjacent content in place (a transcript, a long
 * value). The counterpart of {@link TextLink} — ink says which:
 *
 *   blue + `role="link"` (`Link`)   → leaves this surface
 *   muted underline (this)          → reveals more of it, right here
 *
 * Anything that mutates carries a control surface instead (`Button`, `InlineButton`; composition.md
 * §"Commit & feedback surfaces"). A component because the contract is easy to break: a `<button>`, never
 * a link (which announces leaving); muted, never blue; reveal only. Not `Accordion` (list-row furniture),
 * nor `Button color="muted"` (no affordance until hover, invisible to keyboard and touch).
 */
export declare function TextDisclosure(props: TextDisclosureProps): React.JSX.Element;