import { ResolvedSelectorConfig } from '../types';
/**
 * Shared helper that the `stableId` strategy (in this PR) and the
 * `fallback-css-path` walker (in the orchestration PR) both consult to decide
 * whether an element's id is usable as a selector anchor.
 *
 * Resolution order:
 *
 *   1. Check the customer's explicit-tracking attribute. If set with an empty
 *      value (e.g. `data-amp-track-id=""`), that's an explicit suppression
 *      signal — the customer is telling us to ignore this element's id even
 *      if it would otherwise look stable. Return null.
 *   2. Read the element's id. If absent or empty, return null.
 *   3. Check the id against the autogenerated-id pattern pack. If matched,
 *      return null (the algorithm should walk past this element).
 *   4. Otherwise return the id.
 *
 * The single point of consultation means the strategy and the fallback always
 * agree on what's a usable id — no chance of one component filtering an id
 * while another uses it anyway.
 */
export declare function getStableId(el: Element, cfg: ResolvedSelectorConfig): string | null;
//# sourceMappingURL=get-stable-id.d.ts.map