@mushi-mushi/web 1.7.2 → 1.7.5

package/dist/index.d.cts

@@ -179,6 +179,34 @@ declare class MushiWidget {
     }): void;
     setRewardsState(state: WidgetRewardsState | null): void;
     destroy(): void;
+    /**
+     * Apply the SDK-owned pass-through layout to the host element so it is
+     * always zero-sized and click/touch-transparent. Only the shadow-root
+     * internals (`.mushi-trigger`, `.mushi-banner`, `.mushi-panel`) opt back
+     * into pointer events.  This is idempotent and safe to call repeatedly.
+     */
+    private syncHostChromeState;
+    /**
+     * Returns true when a DOM element matching `hideOnSelector` is currently
+     * present in the host document.  Used by both the trigger and the banner
+     * so a single selector consistently hides ALL SDK-injected launcher
+     * surfaces.  Invalid selectors are swallowed silently (non-fatal).
+     */
+    private isSuppressedByHost;
+    /**
+     * Returns a snapshot of the widget's host-layer health for use in
+     * `Mushi.diagnose()`.  Callers check this to know whether the widget
+     * could ever block host-app UI without opening a browser devtools.
+     */
+    getWidgetDiagnostics(): {
+        widgetHostPointerSafe: boolean;
+        widgetHostBounds: {
+            width: number;
+            height: number;
+        } | null;
+        widgetSuppressed: boolean;
+        bannerRendered: boolean;
+    };
     private syncAttachedLaunchers;
     private syncSmartHide;
     private shouldRenderTrigger;
@@ -195,6 +223,16 @@ declare class MushiWidget {
     private isRouteHidden;
     private getTheme;
     private render;
+    /**
+     * Queries each `avoidSelectors` element in the host document and returns
+     * the minimum top-offset in px so that a top-anchored element clears all
+     * of them by `gap` pixels. Returns `null` when no selectors are provided
+     * or no matching elements have a non-zero bounding rect.
+     *
+     * Runs in the host document (not shadow DOM) so it can reach fixed headers,
+     * sticky nav bars, and sign-in CTAs.
+     */
+    private computeAvoidTopPx;
     private applyInsetVars;
     private renderStep;
     private renderOutdatedBanner;
@@ -397,6 +435,19 @@ interface ProactiveConfig {
     maxProactivePerSession: number;
     dismissCooldownHours: number;
     suppressAfterDismissals: number;
+    /**
+     * Cross-reload re-show cooldown, in minutes. When a proactive trigger is
+     * granted a show, the SDK persists a `mushi:lastShown` timestamp. On a fresh
+     * session (a brand-new JS context after a page reload or crash, before this
+     * manager has shown anything itself) prompts are suppressed if one was shown
+     * within this window — even if the user never cleanly dismissed it.
+     *
+     * The 24h `dismissCooldownHours` only engages once `recordDismissal()` runs,
+     * which requires a clean widget `onClose`. A reloading/broken page tears down
+     * the JS context before that, so without this guard the panel re-pops on every
+     * load. Set to `0` to disable (legacy behavior). Defaults to 30 minutes.
+     */
+    reshowCooldownMinutes: number;
 }
 interface ProactiveManager {
     shouldShow(triggerType: string): boolean;

package/dist/index.d.ts

@@ -179,6 +179,34 @@ declare class MushiWidget {
     }): void;
     setRewardsState(state: WidgetRewardsState | null): void;
     destroy(): void;
+    /**
+     * Apply the SDK-owned pass-through layout to the host element so it is
+     * always zero-sized and click/touch-transparent. Only the shadow-root
+     * internals (`.mushi-trigger`, `.mushi-banner`, `.mushi-panel`) opt back
+     * into pointer events.  This is idempotent and safe to call repeatedly.
+     */
+    private syncHostChromeState;
+    /**
+     * Returns true when a DOM element matching `hideOnSelector` is currently
+     * present in the host document.  Used by both the trigger and the banner
+     * so a single selector consistently hides ALL SDK-injected launcher
+     * surfaces.  Invalid selectors are swallowed silently (non-fatal).
+     */
+    private isSuppressedByHost;
+    /**
+     * Returns a snapshot of the widget's host-layer health for use in
+     * `Mushi.diagnose()`.  Callers check this to know whether the widget
+     * could ever block host-app UI without opening a browser devtools.
+     */
+    getWidgetDiagnostics(): {
+        widgetHostPointerSafe: boolean;
+        widgetHostBounds: {
+            width: number;
+            height: number;
+        } | null;
+        widgetSuppressed: boolean;
+        bannerRendered: boolean;
+    };
     private syncAttachedLaunchers;
     private syncSmartHide;
     private shouldRenderTrigger;
@@ -195,6 +223,16 @@ declare class MushiWidget {
     private isRouteHidden;
     private getTheme;
     private render;
+    /**
+     * Queries each `avoidSelectors` element in the host document and returns
+     * the minimum top-offset in px so that a top-anchored element clears all
+     * of them by `gap` pixels. Returns `null` when no selectors are provided
+     * or no matching elements have a non-zero bounding rect.
+     *
+     * Runs in the host document (not shadow DOM) so it can reach fixed headers,
+     * sticky nav bars, and sign-in CTAs.
+     */
+    private computeAvoidTopPx;
     private applyInsetVars;
     private renderStep;
     private renderOutdatedBanner;
@@ -397,6 +435,19 @@ interface ProactiveConfig {
     maxProactivePerSession: number;
     dismissCooldownHours: number;
     suppressAfterDismissals: number;
+    /**
+     * Cross-reload re-show cooldown, in minutes. When a proactive trigger is
+     * granted a show, the SDK persists a `mushi:lastShown` timestamp. On a fresh
+     * session (a brand-new JS context after a page reload or crash, before this
+     * manager has shown anything itself) prompts are suppressed if one was shown
+     * within this window — even if the user never cleanly dismissed it.
+     *
+     * The 24h `dismissCooldownHours` only engages once `recordDismissal()` runs,
+     * which requires a clean widget `onClose`. A reloading/broken page tears down
+     * the JS context before that, so without this guard the panel re-pops on every
+     * load. Set to `0` to disable (legacy behavior). Defaults to 30 minutes.
+     */
+    reshowCooldownMinutes: number;
 }
 interface ProactiveManager {
     shouldShow(triggerType: string): boolean;