import 'rollup-plugin-inject-process-env'; /** * Body attribute a host page sets to declare "a form widget already *is* this page". * * The standalone contact/booking page (contact.xapp.ai, book.xapp.ai, sche.dule.pro) * renders a docked form-widget as its whole content and then injects the chat widget on * top of it. Without a signal, the injected widget cheerfully offers two more ways into * the same form - an ActionBar Contact/Book button and the form-widget's own side button. * * This is a declaration, not a detection: the page knows what it renders, the widget does * not. Sniffing the DOM for a docked form would be guesswork, and it would also fire on * pages that legitimately embed a form *and* want a separate one from the bar. * * The writer is `@xapp/form-widget`'s `useFormPageMarker` (used by `@xapp/contact-app`). * The two packages ship independently, so this string is the contract between them - * the same arrangement `[data-xapp-form-side-button]` already uses. Do not rename it on * one side only. XappMedia/chat-widget#1626. */ export declare const FORM_PAGE_ATTRIBUTE = "data-xapp-form-page"; /** * Whether a form widget is already the page, per the marker above. */ export declare function isFormPage(): boolean; /** * Reactive form of {@link isFormPage}. * * The marker and the chat widget mount independently - the widget arrives from a * `