@burdenoff/fe-libs 2026.1029.1 → 2026.1029.3

package/dist/shared/components/assistantWidget/assistantWidgetPosition.d.ts

@@ -0,0 +1,32 @@
+/**
+ * Where the legacy `AssistantWidget` launcher and floating window sit.
+ *
+ * ★★ On an installed (Capacitor / PWA) build below 768px the shell's
+ * `MobileTabBar` is a `fixed bottom-0 z-[60]` bar that publishes its measured
+ * height as `--mobile-tabbar-height` on `<html>`. A launcher pinned at a plain
+ * `bottom-6` (z-[100]) paints over the tab bar's last item ("More") and takes
+ * every tap meant for it, and a window opened at a plain `bottom-24` overlaps
+ * the lifted launcher's close button (BOFF-9679). Both positions therefore add
+ * the same bottom-chrome clearance `AssistantOverlay` uses
+ * (`ASSISTANT_BOTTOM_CHROME_CLEARANCE`): the LARGER of the tab bar height and
+ * the safe area, never their sum. On the web and on desktop every term is
+ * `0px`, so the positions resolve to the original `bottom-6` / `bottom-24`.
+ *
+ * These are Tailwind classes rather than inline styles on purpose: a host's
+ * `launcherClassName` (e.g. `max-md:bottom-24` to clear an MFE-owned tab bar)
+ * must still be able to override the launcher's `bottom`, and an inline style
+ * would silently win over it. Tailwind only generates arbitrary-value
+ * utilities it can see as complete literal strings, so each class is spelled
+ * out in full; `assistantWidgetPosition.test.ts` pins them to the shared
+ * clearance so the two cannot drift apart.
+ */
+/** The launcher: its canonical 1.5rem inset, above the bottom chrome. */
+export declare const ASSISTANT_WIDGET_LAUNCHER_BOTTOM_CLASS = "bottom-[calc(1.5rem+max(var(--mobile-tabbar-height,0px),var(--safe-bottom,0px),env(safe-area-inset-bottom,0px)))]";
+/** The floating window: 6rem up (clear of the 3.5rem launcher), above the bottom chrome. */
+export declare const ASSISTANT_WIDGET_WINDOW_BOTTOM_CLASS = "bottom-[calc(6rem+max(var(--mobile-tabbar-height,0px),var(--safe-bottom,0px),env(safe-area-inset-bottom,0px)))]";
+/**
+ * The floating window's height cap: the viewport less its 6rem bottom inset,
+ * a 1rem top margin and the same clearance, so lifting it never pushes its
+ * header off the top of a short phone screen.
+ */
+export declare const ASSISTANT_WIDGET_WINDOW_MAX_HEIGHT_CLASS = "max-h-[calc(100vh-7rem-max(var(--mobile-tabbar-height,0px),var(--safe-bottom,0px),env(safe-area-inset-bottom,0px)))]";

package/dist/shared/components/assistantWidget/assistantWidgetPosition.js

@@ -0,0 +1,4 @@
+//#region src/shared/components/assistantWidget/assistantWidgetPosition.ts
+var e = "bottom-[calc(1.5rem+max(var(--mobile-tabbar-height,0px),var(--safe-bottom,0px),env(safe-area-inset-bottom,0px)))]", t = "bottom-[calc(6rem+max(var(--mobile-tabbar-height,0px),var(--safe-bottom,0px),env(safe-area-inset-bottom,0px)))]", n = "max-h-[calc(100vh-7rem-max(var(--mobile-tabbar-height,0px),var(--safe-bottom,0px),env(safe-area-inset-bottom,0px)))]";
+//#endregion
+export { e as ASSISTANT_WIDGET_LAUNCHER_BOTTOM_CLASS, t as ASSISTANT_WIDGET_WINDOW_BOTTOM_CLASS, n as ASSISTANT_WIDGET_WINDOW_MAX_HEIGHT_CLASS };