import * as i0 from '@angular/core';

/** Outcome of a clipboard read or permission probe. */
type WrClipboardPermission = 'granted' | 'denied' | 'prompt' | 'unsupported';

/**
 * Programmatic clipboard read / write.
 *
 * - **Write** uses `navigator.clipboard.writeText` with a hidden
 *   `<textarea>` + `execCommand('copy')` fallback for non-secure contexts.
 * - **Read** uses `navigator.clipboard.readText` (no fallback — older
 *   browsers expose no equivalent).
 * - **Available** / **permission** check what the current browser allows
 *   so UI can disable the action when it would silently no-op.
 *
 * SSR-safe: every method short-circuits when there's no `document.defaultView`.
 *
 * @example
 * ```ts
 * const clip = inject(WrClipboard);
 *
 * await clip.write('Hello');           // resolves to true on success
 * const text = await clip.read();      // string | null
 * clip.available();                    // boolean
 * await clip.permission('write');      // 'granted' | 'denied' | 'prompt' | 'unsupported'
 * ```
 *
 * @see https://ngwr.dev/services/clipboard
 */
declare class WrClipboard {
    private readonly doc;
    /** Is any clipboard write path available (async API or `execCommand`)? */
    available(): boolean;
    /**
     * Write text. Resolves to `true` on success, `false` on failure (denied
     * permission, no clipboard, etc).
     */
    write(text: string): Promise<boolean>;
    /**
     * Read text from the clipboard. Returns `null` when unsupported or
     * when the user denied the permission prompt.
     */
    read(): Promise<string | null>;
    /**
     * Report whether clipboard read / write is available and, when the
     * browser exposes it, what the user has granted.
     *
     * The answer is grounded in the actual Clipboard API capability
     * (`writeText` / `readText`), then refined by the Permissions API when
     * it can speak for the requested name. `clipboard-read` / `clipboard-write`
     * are not recognised everywhere — Firefox and Safari throw on the query —
     * so a missing or throwing Permissions API is treated as "supported,
     * will resolve at use time" (`'prompt'`), not `'unsupported'`. We only
     * return `'unsupported'` when the capability genuinely isn't there.
     */
    permission(name: 'read' | 'write'): Promise<WrClipboardPermission>;
    /** Hidden-textarea + `execCommand('copy')` write. Synchronous, no permissions. */
    private legacyWrite;
    static ɵfac: i0.ɵɵFactoryDeclaration<WrClipboard, never>;
    static ɵprov: i0.ɵɵInjectableDeclaration<WrClipboard>;
}

export { WrClipboard };
export type { WrClipboardPermission };