/**
 * Backward compatibility for the editing surfaces that predate this module.
 *
 * The new architecture is the default for every editable column, which means it
 * has to keep two older mechanisms working exactly as they did:
 *
 * 1. **`ColumnDef.renderer.editor`** — a bare `(params) => HTMLElement` slot.
 *    It took priority over every built-in editor, so its replacement strategy
 *    sits immediately after the editability check.
 * 2. **The `dropdown` / `object` dropdown** — `CustomDropdownEditor`, a
 *    virtualised, option-renderer-aware list that is materially nicer than a
 *    native `<select>`. Rewriting those columns onto the plain `select` editor
 *    would be a visible downgrade, so it is wrapped rather than replaced.
 *
 * Both are adapters, not forks: each presents an {@link ICellEditor} to the
 * resolver like everything else, so the pipeline has exactly one code path and
 * these can be deleted the day the old surfaces are.
 *
 * @packageDocumentation
 */
import type { EditorRendererParams } from '../../types/renderer.types';
import type { CellEditorParams, ICellEditor } from '../types/cell-editor.types';
import type { EditorResolutionStrategy } from '../registry/default-editor-resolver';
/**
 * Presents a legacy `renderer.editor` function as an {@link ICellEditor}.
 *
 * The old contract had no `getValue`: the slot reported values through
 * `onValueChange` and the engine remembered the last one. That is reproduced
 * here — {@link getValue} returns whatever was last reported — so a column using
 * the slot behaves identically while still flowing through validation, the
 * popup service and the keyboard manager like any other editor.
 */
export declare class LegacySlotEditor implements ICellEditor {
    private readonly render;
    private gui;
    private value;
    /**
     * @param render - The function from `ColumnDef.renderer.editor`.
     */
    constructor(render: (params: EditorRendererParams) => HTMLElement);
    init(params: CellEditorParams): void;
    getGui(): HTMLElement;
    getValue(): unknown;
}
/**
 * Presents {@link CustomDropdownEditor} as an {@link ICellEditor}.
 *
 * That class owns its own portal, virtual scrolling, keyboard handling and
 * dismissal, so this wrapper is deliberately thin: it reports `isPopup(): false`
 * because the dropdown portals its *panel* itself while its trigger stays in the
 * cell, and it hands the grid a hidden host element to satisfy the `getGui`
 * contract.
 */
export declare class LegacyDropdownEditor implements ICellEditor {
    private dropdown;
    private host;
    private value;
    private tabBackwards;
    init(params: CellEditorParams): void;
    getGui(): HTMLElement;
    getValue(): unknown;
    /** The dropdown focuses its own trigger; nothing extra to do. */
    focus(): void;
    destroy(): void;
}
/**
 * Resolution strategy for a column carrying a legacy `renderer.editor` slot.
 *
 * Inserted directly after the editability check so it keeps the priority it has
 * always had: the slot wins over every built-in editor, and over `cellEditor`,
 * because a column that declares both was written against the old behaviour.
 */
export declare const legacySlotStrategy: EditorResolutionStrategy;
/**
 * Resolution strategy keeping `dropdown` / `object` columns on the rich
 * dropdown.
 *
 * Sits immediately before the column-type default, so an explicit
 * `cellEditor: 'select'` still opts a column into the native select — the
 * override the new API is supposed to offer — while a column that says nothing
 * keeps the UX it has today.
 */
export declare const legacyDropdownStrategy: EditorResolutionStrategy;
//# sourceMappingURL=legacy-editors.d.ts.map