@maildeno/editor 0.4.5 → 0.4.7

package/dist/lightDom.d.ts

@@ -1,30 +0,0 @@
-/**
- * Mounts the editor directly into the page, with no shadow root.
- *
- * This is the `shadowDom: false` path. Shadow DOM buys style isolation,
- * but it costs real behaviour: `event.target` is retargeted to the host,
- * `document.activeElement` returns the host rather than the focused
- * element, `document.querySelector` cannot see inside, and `@font-face`
- * and `@property` are ignored entirely. Every one of those has caused a
- * concrete bug in this package, and third-party libraries hit them too —
- * Reka UI's own internals use `document.activeElement` and never
- * `composedPath()`, so anything built on it can misbehave inside a shadow
- * root in ways that cannot be fixed from the outside.
- *
- * Light DOM trades isolation for predictability: the host page's CSS can
- * reach the editor (and vice versa), but every browser API behaves
- * normally. It is the right choice when the host page's styles are known
- * and controlled, and the escape hatch when something in the shadow path
- * misbehaves.
- */
-export interface LightDomMount {
-    /** The element the editor was mounted into. */
-    element: HTMLElement;
-    /** Reads EmailEditor.vue's defineExpose'd methods. */
-    exposed: () => Record<string, any> | null;
-    setProp: (key: string, value: unknown) => void;
-    addSaveHandler: (fn: (payload: any) => void) => void;
-    removeSaveHandler: (fn: (payload: any) => void) => void;
-    destroy: () => void;
-}
-export declare function mountLightDom(container: HTMLElement, initialProps: Record<string, unknown>): LightDomMount;

package/dist/shadowStyles.d.ts

@@ -1,8 +0,0 @@
-/**
- * False when running from source, where the build-time substitution above
- * never ran and the shadow root therefore has no component CSS. Used to
- * decide whether the dev style mirror is needed — a capability check rather
- * than an environment guess, so it self-corrects in either direction.
- */
-export declare function hasExtractedScopedCss(): boolean;
-export declare function buildShadowStyles(): string[];

package/dist/utils/generateId.d.ts

@@ -1 +0,0 @@
-export declare const generateId: () => string;

package/dist/utils/shadowDom.d.ts

@@ -1,30 +0,0 @@
-/**
- * Shadow-DOM-safe replacements for the two DOM lookups that silently do
- * the wrong thing inside a shadow root.
- *
- * Both are easy to get wrong because they fail *quietly* and only in the
- * custom-element build — the plain Vue path keeps working, so the bug
- * looks framework-specific when it is really about the shadow boundary.
- */
-/**
- * `document.activeElement` returns the shadow **host** for anything
- * focused inside a shadow root, never the element that actually has
- * focus. This walks down through nested shadow roots to the real one.
- *
- * Without it, any `container.contains(document.activeElement)` check
- * reads as false for every element inside the editor — which is what made
- * the rich-text toolbar tear itself down the moment you clicked its font
- * Select, merge-tag picker, or colour picker.
- */
-export declare function deepActiveElement(): Element | null;
-/**
- * `document.querySelector` cannot see into a shadow root. Querying from
- * an element's own root node instead returns the ShadowRoot when mounted
- * inside one and the Document otherwise, so the same call is correct for
- * both usage paths with no branching.
- */
-export declare function queryFromRoot<E extends Element = Element>(from: Element | null | undefined, selector: string): E | null;
-/**
- * `document.querySelectorAll` equivalent of {@link queryFromRoot}.
- */
-export declare function queryAllFromRoot<E extends Element = Element>(from: Element | null | undefined, selector: string): E[];