/**
 * View control for rendered reveal.js slideshows.
 *
 * A built deck opens as a presentation: one slide at a time, arrow keys to
 * advance. That is what an audience should see and a poor way to *write* a
 * deck — an author wants the whole thing at once, scrolling like every other
 * preview in the editor. reveal.js has exactly that built in (its "scroll
 * view"), and this module turns it on.
 *
 * ## Why a script, and why this one
 *
 * Reveal reads `view: 'scroll'` from the config passed to `Reveal.initialize`,
 * and only there: internally the activation runs once, from the routine that
 * fires after plugins load, so a later `Reveal.configure({view: 'scroll'})`
 * sets the value but activates nothing. The URL form (`?view=scroll`) is no
 * help either — the extension assigns `webview.html` directly, so there is no
 * query string of ours for reveal to parse.
 *
 * That leaves the config object, which PreTeXt writes into the page as a
 * literal at the end of the document. Rather than rewrite that literal — which
 * would bind us to its exact emitted text — {@link revealBridgeScript} wraps
 * `Reveal.initialize` itself and merges the overrides over whatever the deck
 * passes. The script is injected immediately after reveal.js's own `<script
 * src>`: classic scripts run in order, so it is guaranteed to see `Reveal`
 * defined and to run before the deck's initialize call.
 *
 * ## Switching views
 *
 * By re-rendering the page, not by talking to a live deck. The scroll view
 * restructures the DOM extensively and `Reveal.destroy()` does not fully undo
 * it, so a destroy/re-initialize toggle leaves debris. Since the embedder
 * already holds the rendered HTML, switching views is just re-injecting with
 * the other value and re-assigning it — no re-render, no reveal internals.
 */
/**
 * How a rendered deck is presented.
 *
 * - "slides" - reveal.js as built: one slide at a time. What an audience sees.
 * - "scroll" - the whole deck as one continuous scroll. Better for authoring.
 */
export type RevealView = "slides" | "scroll";
/** True when `value` is one of the {@link RevealView} strings. */
export declare function isRevealView(value: unknown): value is RevealView;
/** Tuning for how a deck is laid out in the preview. */
export interface RevealViewOptions {
    /**
     * How large a deck's content is drawn, as a fraction of its presented size,
     * between 0.25 and 1. Zooming out shrinks the text rather than the slide —
     * the slide stays the same size on screen and more of its content fits
     * inside, which is the only way to read content that overflows a slide (see
     * {@link zoomedSlideSize}). Scroll view only. Defaults to
     * {@link DEFAULT_REVEAL_ZOOM}.
     */
    zoom?: number;
}
/**
 * Zoom when the caller states none: the deck exactly as it will be presented.
 */
export declare const DEFAULT_REVEAL_ZOOM = 1;
/**
 * The inline `<script>` (as a string) that applies `view` to a rendered deck.
 *
 * Written in ES5-ish, self-contained JS: it is embedded verbatim in the output
 * page, so no bundler runs over it, and it re-executes on every in-place
 * `document.write` rebuild the extension performs.
 */
export declare function revealBridgeScript(view: RevealView, options?: RevealViewOptions): string;
/**
 * Inject the view bridge into a rendered slideshow, immediately after
 * reveal.js's own `<script src>`.
 *
 * Returns the page unchanged when that tag is not found — which means either
 * the page is not a deck, or upstream has changed how reveal.js is loaded. In
 * both cases the deck still works, just in its built-in view, and a silently
 * ordinary slideshow is a far better outcome than a thrown error in a preview.
 */
export declare function injectRevealBridge(html: string, view: RevealView, options?: RevealViewOptions): string;