import type { ReactNode } from "react";
export type FileDropZoneProps = {
    /** An `accept` list, passed straight to the input. */
    accept?: string;
    className?: string;
    /** Secondary line — the formats taken, a size cap. */
    description?: ReactNode;
    isDisabled?: boolean;
    isMultiple?: boolean;
    /** The control's accessible name, and its visible prompt. */
    label: string;
    onDropFiles: (files: File[]) => void;
    /**
     * Dropped text, when there is any. A browser hands over a dragged
     * link as `text/plain` and no files at all, which is what
     * gallery-downloader's page is built entirely around — it takes
     * `dataTransfer.getData("text")` and never looks at `.files`.
     */
    onDropText?: (text: string) => void;
};
/**
 * The one drag target in the fleet is gallery-downloader's, and it
 * gets the hard part right: `dragenter`/`dragleave` fire once per
 * *element* the pointer crosses, not once per zone, so a naive
 * implementation flickers over every child — and that page keeps a
 * `dragDepth` counter, which is the correct fix. It is reproduced
 * below with credit.
 *
 * What it has no answer for is the part that cannot be fixed by
 * counting:
 *
 * ### Dragging is pointer-only, so the zone is a label around an input
 *
 * There is **no keyboard gesture for drag-and-drop**. WCAG 2.5.7
 * (AA since 2.2) requires a single-pointer alternative for any
 * dragging movement, and the honest one has existed since 1995: a
 * real `<input type="file">`. So this component is a `<label>`
 * wrapping a visually-hidden input — the whole zone is the label's
 * click target, Tab reaches the input, Space and Enter open the
 * picker, and the drop handlers are an *enhancement* on top of a
 * control that already works without them.
 *
 * That ordering is the entire design. Building the drop zone first
 * and bolting on a "or browse" link is how the fleet's version ended
 * up with an `alert()` as its error channel and no keyboard path at
 * all.
 *
 * ### `dragover` must be prevented, and the reason is a footgun
 *
 * A browser's default for `dragover` is *reject the drop*. Not
 * preventing it means `drop` never fires — nothing errors, the
 * cursor shows a "no entry" sign, and the zone looks like it has a
 * broken handler when it in fact has no handler running at all.
 *
 * ### It reports text as well as files
 *
 * Dragging a link gives you `text/plain` and an empty `files` list.
 * A zone that only reads `.files` silently ignores the single most
 * common thing a user drags into a downloader, which is why
 * `onDropText` is here rather than being someone's follow-up.
 */
export declare const FileDropZone: ({ accept, className, description, isDisabled, isMultiple, label, onDropFiles, onDropText, }: FileDropZoneProps) => ReactNode;
//# sourceMappingURL=FileDropZone.d.ts.map