@marketrix.ai/widget 3.8.476 → 3.8.478

package/dist/src/components/blocks/Notifications.d.ts

@@ -0,0 +1,29 @@
+import { Toast } from '@base-ui/react/toast';
+import React from 'react';
+export declare const GREETING_TIMEOUT_MS = 8000;
+export interface NotificationProviderProps {
+    children?: React.ReactNode;
+    /** The closed shadow root to portal into — a portal to document.body would leave the styles behind. */
+    container?: HTMLElement | null;
+    /** Raised above the launcher when the launcher sits at the bottom, so the two cannot overlap. */
+    offsetBottom?: number;
+}
+/**
+ * The one notification surface. Base UI owns the live region, the dismiss timers, hover-to-pause and
+ * stacking; before this the widget announced nothing to a screen reader and ran its own setTimeout.
+ */
+export declare const NotificationProvider: React.FC<NotificationProviderProps>;
+export declare const useNotifications: typeof Toast.useToastManager;
+export interface WidgetNotificationsProps {
+    error?: string;
+    onClearError: () => void;
+    onRetry?: () => void;
+    greeting?: string;
+    greetingBody?: string;
+    onGreetingDismiss: () => void;
+}
+/**
+ * Drives the toasts from widget state. Both use a stable id, so `add` upserts and a re-render cannot
+ * stack duplicates of the same condition.
+ */
+export declare const WidgetNotifications: React.FC<WidgetNotificationsProps>;

package/dist/src/components/blocks/WidgetDialog.d.ts

@@ -7,5 +7,11 @@ export interface WidgetDialogProps {
     onConfirm?: () => void;
     confirmLabel?: string;
     cancelLabel?: string;
+    /**
+     * Where focus lands on close. Base UI's default restore is broken here: it descends
+     * `element.shadowRoot.activeElement`, which is null for a CLOSED root, so it records the shadow
+     * HOST and hands focus to a host-page element on close. Naming the target sidesteps that.
+     */
+    finalFocusRef?: React.RefObject<HTMLElement | null>;
 }
 export declare const WidgetDialog: React.FC<WidgetDialogProps>;

package/dist/src/components/navigation/ShellTabBar.d.ts

@@ -1,7 +1,3 @@
 import React from 'react';
-import type { WidgetView } from '../../types';
-export interface ShellTabBarProps {
-    activeView: WidgetView;
-    onChange: (view: WidgetView) => void;
-}
-export declare const ShellTabBar: React.FC<ShellTabBarProps>;
+/** Selection, roles, ids and arrow-key navigation come from Tabs.Root — see MessengerShell. */
+export declare const ShellTabBar: React.FC;

package/dist/src/utils/validation.d.ts

@@ -1,4 +1,17 @@
-import type { ZodError } from 'zod';
+import type { WidgetSettingsData } from '../sdk';
 export declare function isHTMLElement(element: Element | null): element is HTMLElement;
 export declare function isHTMLScriptElement(element: Element | null): element is HTMLScriptElement;
-export declare const invalidSettingsMessage: (error: ZodError) => string;
+export type WidgetSettingsResult = {
+    settings: WidgetSettingsData;
+    invalidFields?: undefined;
+} | {
+    settings?: undefined;
+    invalidFields: string[];
+};
+/**
+ * Validates and PICKS, because stripping is load-bearing: `widgetDefaultGet` returns the render
+ * constants too, and the settings object is spread into the widget config — passing unknown keys
+ * through would leak them where zod used to drop them.
+ */
+export declare function parseWidgetSettings(value: unknown): WidgetSettingsResult;
+export declare const invalidSettingsMessage: (invalidFields: string[]) => string;