/**
 * Helpers that tell where an input event came from. Deliberately NOT re-exported through
 * `Handsontable.dom` (see `src/index.ts`): the detection is a browser-quirk heuristic that may
 * change, so it stays internal.
 */
/**
 * How long (ms) after a touch gesture the browser-synthesized `mousedown`/`mouseup`/`click`
 * sequence is still expected when the engine does not report the input origin (WebKit,
 * Firefox). Shared by Walkontable's mouse listeners and TableView's outside-click handling so
 * both layers use the same fallback window.
 *
 * Ceiling, not a target: Walkontable drops only the first `mousedown`/`mouseup` pair after a tap
 * (see `#synthesizedPairPending`), so the constant only bounds how long that pair may take to
 * arrive; browsers deliver it within a few hundred milliseconds, which this value covers with
 * margin. On engines that do not report the input origin (WebKit, Firefox) a real mouse event
 * that arrives inside the ceiling BEFORE the synthesized pair — e.g. a first tap on an unselected
 * cell is `preventDefault`-ed and synthesizes nothing, so the pair never comes — is still
 * dropped: that includes a fill-handle grab or a drag-selection started with a mouse or trackpad
 * within half a second of such a tap. A pair that straddles the ceiling yields one unpaired
 * `mouseup` (the `mousedown` is dropped, the `mouseup` is processed and clears the pending pair).
 * Besides a first tap on an unselected cell, a long-press synthesizes no pair either, so the
 * pending pair stays armed for the same ceiling after it.
 */
export declare const TOUCH_SYNTHESIZED_MOUSE_WINDOW = 500;
/**
 * Returns whether a mouse event was synthesized from a touch gesture, as reported by the browser
 * (`sourceCapabilities.firesTouchEvents`, Blink only) — `true`/`false` when reported, `undefined`
 * when the engine does not tell (WebKit, Firefox, script-dispatched events). Browsers that fire
 * touch events synthesize a `mousedown`/`mouseup`/`click` sequence after `touchend` for
 * compatibility. Only Blink exposes the origin; WebKit and Firefox do not, and script-dispatched
 * events carry `null`. In those cases the function returns `undefined` so the caller can fall back
 * to a timing heuristic.
 *
 * @param {Event} event The mouse event object.
 * @returns {boolean|undefined} `true` when synthesized from touch, `false` when it comes from a
 *                              non-touch device, `undefined` when the browser does not tell.
 */
export declare function getMouseEventTouchOrigin(event: Event): boolean | undefined;