@eshal-bot/chat-widget 0.1.122 → 0.1.123

package/dist/chat-widget.esm.js

@@ -1 +1 @@
-export{S as default}from"./chat-widget-index-CbBUA9Lj.esm.js";import"react";import"react-dom/client";import"react-dom";import"react/jsx-runtime";
+export{S as default}from"./chat-widget-index-Bn-k9Jjr.esm.js";import"react";import"react-dom/client";import"react-dom";import"react/jsx-runtime";

package/dist/chat-widget.js

@@ -16627,6 +16627,11 @@
       };
     }, [isVoiceSessionActive, voiceStatus]);
     const normalizedDisclaimerLinkUrl = reactExports.useMemo(() => normalizeExternalUrl(disclaimerLinkUrl), [disclaimerLinkUrl]);
+
+    // EV-2351: the disclaimer's direction comes from its own text. Falls back to
+    // the configured `isRtl` when the text has no strongly-directional character
+    // (digits, punctuation, emoji only), same contract as the message bubbles.
+    const disclaimerIsRtl = reactExports.useMemo(() => detectTextDirection(disclaimerText, isRtl), [disclaimerText, isRtl]);
     return /*#__PURE__*/jsxRuntimeExports.jsxs(jsxRuntimeExports.Fragment, {
       children: [disclaimerEnabled && disclaimerText && disclaimerPosition === "top" && /*#__PURE__*/jsxRuntimeExports.jsx("div", {
         className: "flex justify-center",
@@ -16636,13 +16641,21 @@
             color: isDark ? "#d1d5db" : "#6b7280",
             fontFamily: fontFamily !== undefined && fontFamily !== null ? fontFamily : "Inter",
             fontSize: fontSize !== undefined && fontSize !== null ? "calc(".concat(fontSize, " - 2px)") : "12px",
-            direction: isRtl ? "rtl" : "ltr",
+            // EV-2351: direction from the disclaimer's OWN text, not from
+            // the configured default language. This is static configured
+            // copy rather than message content, which is why the earlier
+            // per-message passes never reached it - an English disclaimer
+            // under an Arabic-default concierge rendered with its trailing
+            // period pushed to the front (".Please verify important
+            // information"). Same helper and same fallback as the message
+            // bubbles below.
+            direction: disclaimerIsRtl ? "rtl" : "ltr",
             textAlign: "center",
             borderColor: isDark ? "#374151" : "#e5e7eb"
           },
           children: /*#__PURE__*/jsxRuntimeExports.jsxs("p", {
             className: "leading-relaxed whitespace-pre-wrap break-words inline",
-            dir: isRtl ? "rtl" : "ltr",
+            dir: disclaimerIsRtl ? "rtl" : "ltr",
             style: {
               color: isDark ? "#d1d5db" : "#6b7280",
               fontFamily: fontFamily !== undefined && fontFamily !== null ? fontFamily : "Inter",
@@ -17107,24 +17120,42 @@
         return;
       }
 
-      // presignRes.ok means decideAttachmentPolicy's LAST step ran -
-      // addSessionBytes already reserved this file's bytes server-side.
-      // Mark it so removeAttachment (and every error path below) knows to
-      // call /release rather than just correcting the client estimate.
-      patchAttachment(attachmentId, {
-        reservedBytes: file.size
-      });
+      // How many bytes the SERVER is currently holding for this attachment.
+      // Only ever non-zero when we know a reservation exists (EV-2791) -
+      // releasing bytes the server never reserved silently hands the
+      // conversation extra budget, which is as wrong as over-counting.
+      let heldServerBytes = 0;
+      const releaseHeld = () => {
+        if (heldServerBytes > 0) {
+          releaseSessionBytes({
+            apiEndpoint,
+            conversationId,
+            size: heldServerBytes,
+            authHeader
+          });
+          heldServerBytes = 0;
+          patchAttachment(attachmentId, {
+            reservedBytes: 0
+          });
+        }
+      };
+      const undoLocalEstimate = () => {
+        sessionBytesRef.current.bytes = Math.max(0, sessionBytesRef.current.bytes - file.size);
+      };
       let presign;
       try {
         presign = await presignRes.json();
       } catch (_unused5) {
+        // Body unreadable, so we cannot tell whether a reservation was made.
+        // Release the declared size - the server clamps at zero, and this
+        // path needs the policy check to have already passed.
         releaseSessionBytes({
           apiEndpoint,
           conversationId,
           size: file.size,
           authHeader
         });
-        sessionBytesRef.current.bytes = Math.max(0, sessionBytesRef.current.bytes - file.size);
+        undoLocalEstimate();
         patchAttachment(attachmentId, {
           reservedBytes: 0
         });
@@ -17132,6 +17163,20 @@
         return;
       }
 
+      // `reserved` tells us whether /presign itself charged the session cap.
+      // It is false on the NFS/multipart branch, where /multipart is the
+      // reserving gate - reserving in both places is what double-counted the
+      // "already used" figure (EV-2791). An older backend omits the field;
+      // fall back to the legacy assumption so a widget deployed ahead of the
+      // backend still releases correctly.
+      const presignReserved = typeof presign.reserved === "boolean" ? presign.reserved : !presign.useMultipart;
+      if (presignReserved) {
+        heldServerBytes = file.size;
+        patchAttachment(attachmentId, {
+          reservedBytes: file.size
+        });
+      }
+
       // Step B - upload bytes. Two paths:
       //   * useMultipart=true → POST FormData to /multipart (NFS + any
       //     backend without a direct-PUT endpoint).
@@ -17160,6 +17205,13 @@
           });
           uploadedReadUrl = multipartResp.url;
           uploadedStorageKey = multipartResp.storageKey;
+          // /multipart is the reserving gate on this path, and it only
+          // reserves once its own policy check passes - the bytes are held
+          // from here on, so removing the chip must release them.
+          heldServerBytes = file.size;
+          patchAttachment(attachmentId, {
+            reservedBytes: file.size
+          });
         } else if (presign.uploadUrl) {
           await putWithProgress({
             url: presign.uploadUrl,
@@ -17186,16 +17238,8 @@
           });
           if (!confirmed.ok) {
             inflightRef.current.delete(attachmentId);
-            releaseSessionBytes({
-              apiEndpoint,
-              conversationId,
-              size: file.size,
-              authHeader
-            });
-            sessionBytesRef.current.bytes = Math.max(0, sessionBytesRef.current.bytes - file.size);
-            patchAttachment(attachmentId, {
-              reservedBytes: 0
-            });
+            releaseHeld();
+            undoLocalEstimate();
             errorPatch(attachmentId, confirmed.code, confirmed.message);
             return;
           }
@@ -17207,16 +17251,12 @@
         // Aborted means removeAttachment already released this reservation -
         // releasing again here would double-count the give-back.
         if (err && err.aborted) return;
-        releaseSessionBytes({
-          apiEndpoint,
-          conversationId,
-          size: file.size,
-          authHeader
-        });
-        sessionBytesRef.current.bytes = Math.max(0, sessionBytesRef.current.bytes - file.size);
-        patchAttachment(attachmentId, {
-          reservedBytes: 0
-        });
+        // On the multipart path a failure means either the policy check
+        // rejected (nothing reserved) or the write failed (the route released
+        // its own reservation) - `heldServerBytes` is 0 either way, so
+        // releaseHeld() correctly does nothing.
+        releaseHeld();
+        undoLocalEstimate();
         errorPatch(attachmentId, "network", "Upload failed. Please retry.");
         return;
       }
@@ -18190,6 +18230,15 @@
     useGoogleFont(resolvedHeaderFontFamily);
     const t = reactExports.useMemo(() => createTranslator(defaultLanguage), [defaultLanguage]);
     const isRtl = isRtlLocale(defaultLanguage);
+
+    // EV-2351: the subtitle is operator-authored copy, so its direction has to
+    // come from the text itself rather than from the configured default
+    // language. With Arabic as the default, an English subtitle inherited the
+    // header's RTL container and rendered with its trailing punctuation pushed
+    // to the front ("!Do what you love. We'll do the rest"). Falls back to the
+    // configured direction when the text carries no strongly-directional
+    // character, same contract as the message bubbles.
+    const subtitleIsRtl = reactExports.useMemo(() => detectTextDirection(subtitle, isRtl), [subtitle, isRtl]);
     const agentStatus = reactExports.useMemo(() => computeAgentStatus({
       showStatus,
       statusMode,
@@ -18270,9 +18319,11 @@
           }), subtitle ? /*#__PURE__*/jsxRuntimeExports.jsx("p", {
             title: subtitle,
             className: "leading-snug truncate opacity-75",
+            dir: subtitleIsRtl ? "rtl" : "ltr",
             style: {
               fontSize: "12px",
-              color: iconColor
+              color: iconColor,
+              textAlign: subtitleIsRtl ? "right" : "left"
             },
             children: subtitle
           }) : null]