@xapp/chat-widget 1.104.1 → 1.105.1

package/dist/index.js

@@ -3871,6 +3871,31 @@ function useVisualViewportProperties(enabled) {
         return trackVisualViewport();
     }, [enabled]);
 }
+/** The sessionStorage key the booking page writes the flag to. */
+var TEST_LEAD_STORAGE_KEY = "xa_test";
+/** The attribute sent with a lead submission. */
+var TEST_LEAD_ATTRIBUTE = "xaTest";
+/** True when the current browser session is a test-lead page view. */
+function isTestLeadSession() {
+    try {
+        return sessionStorage.getItem(TEST_LEAD_STORAGE_KEY) === "1";
+    }
+    catch (_a) {
+        // Storage can be blocked by the browser; treat that as a real visit.
+        return false;
+    }
+}
+/**
+ * Tags the attributes as a test lead when the session flag is set. A test must
+ * never be counted as Google traffic, so any `rwg_token` is dropped as well.
+ */
+function addTestLeadAttribute(attributes) {
+    if (isTestLeadSession()) {
+        attributes[TEST_LEAD_ATTRIBUTE] = true;
+        delete attributes["rwg_token"];
+    }
+    return attributes;
+}
 
 /**
  * Quicker configurable uuid
@@ -3894,6 +3919,7 @@ function uuid() {
 var IconButton_1 = IconButton;
 var RichInput_1 = RichInput;
 var SuggestionsList_1 = SuggestionsList;
+var addTestLeadAttribute_1 = addTestLeadAttribute;
 var findItemByIndex_1 = findItemByIndex;
 var getAttribution_1 = getAttribution;
 var getItemsLength_1 = getItemsLength;
@@ -4129,6 +4155,28 @@ function newMessage() {
 	
 } (cjs));
 
+/**
+ * Did this request fail because it never reached the server?
+ *
+ * The widget used to answer "the server is offline" to every failure, and on 2026-09-25 a retired
+ * Bedrock model made every new chat fail with a 500 — so every visitor was told the server was
+ * offline while it was up and serving. The message sent the investigation at DNS, CORS and CDNs for
+ * 110 minutes and told customers something untrue.
+ *
+ * A status code is the discriminator: it only exists because the server answered. Present means
+ * reachable-but-failing, which is a different message to a visitor and a different thing for us to
+ * go and look at.
+ *
+ * An unrecognised failure counts as transport. It is the safer claim — "cannot reach the server"
+ * when the truth is unknown is wrong in a way the visitor can act on, where leaving the widget
+ * looking hung is not.
+ */
+function isTransportFailure(error) {
+    var status = Number(error === null || error === void 0 ? void 0 : error.statusCode);
+    // A real HTTP status, so the server answered.
+    return !(Number.isFinite(status) && status >= 100 && status <= 599);
+}
+
 /**
  * Default configuration messages
  * @returns
@@ -4564,7 +4612,7 @@ var MCPChat = /** @class */ (function () {
      */
     MCPChat.prototype.initializeNewSession = function () {
         return __awaiter$1(this, void 0, void 0, function () {
-            var endpoint, error_2;
+            var endpoint, error_2, statusCode;
             var _this = this;
             var _a;
             return __generator$1(this, function (_b) {
@@ -4594,11 +4642,18 @@ var MCPChat = /** @class */ (function () {
                         return [3 /*break*/, 5];
                     case 3:
                         error_2 = _b.sent();
-                        err("Failed to initialize new session: ".concat(error_2));
+                        statusCode = error_2 === null || error_2 === void 0 ? void 0 : error_2.statusCode;
+                        err("Failed to initialize new session: ".concat(error_2, ", statusCode: ").concat(statusCode));
                         this.stopTyping();
-                        this.setConnectionStatus("offline");
+                        // Only "offline" when the request never reached the server. A status code means it
+                        // answered, so the server is up and something behind it is broken -- and on 2026-09-25
+                        // a 500 from a retired model put "Server is offline" in front of every visitor, which
+                        // was untrue and sent the investigation at DNS, CORS and CDNs for 110 minutes.
+                        if (isTransportFailure(error_2)) {
+                            this.setConnectionStatus("offline");
+                        }
                         // Show a failure message but don't block - user can still try sending messages
-                        this.sendFailureMessage(0, 0, this.getErrorMessage(error_2));
+                        this.sendFailureMessage(0, 0, this.getErrorMessage(error_2, statusCode));
                         return [3 /*break*/, 5];
                     case 4:
                         this.isInitializingSession = false;
@@ -5130,8 +5185,11 @@ var MCPChat = /** @class */ (function () {
                             this.sendFailureMessage(0, 0, errorMessage);
                             return [2 /*return*/];
                         }
-                        // Set offline status
-                        this.setConnectionStatus("offline");
+                        // Same rule: a 5xx is the server answering, so it is not offline. Left as a
+                        // retryable failure, which is what the loop below treats it as anyway.
+                        if (isTransportFailure(error_4)) {
+                            this.setConnectionStatus("offline");
+                        }
                         if (!isLastAttempt) return [3 /*break*/, 7];
                         statusCode_1 = error_4 === null || error_4 === void 0 ? void 0 : error_4.statusCode;
                         errorMessage = config.text || this.getErrorMessage(error_4, statusCode_1);
@@ -5693,7 +5751,7 @@ var MCPChat = /** @class */ (function () {
     };
     MCPChat.prototype.requestReplay = function () {
         return __awaiter$1(this, void 0, void 0, function () {
-            var error_5;
+            var error_5, statusCode;
             return __generator$1(this, function (_a) {
                 switch (_a.label) {
                     case 0:
@@ -5715,8 +5773,12 @@ var MCPChat = /** @class */ (function () {
                         return [3 /*break*/, 5];
                     case 3:
                         error_5 = _a.sent();
-                        err("[MCPChat] Replay request failed: ".concat(error_5));
-                        this.setConnectionStatus("offline");
+                        statusCode = error_5 === null || error_5 === void 0 ? void 0 : error_5.statusCode;
+                        err("[MCPChat] Replay request failed: ".concat(error_5, ", statusCode: ").concat(statusCode));
+                        // Same rule as session init: a status code means the server answered.
+                        if (isTransportFailure(error_5)) {
+                            this.setConnectionStatus("offline");
+                        }
                         return [3 /*break*/, 5];
                     case 4:
                         this.stopTyping();
@@ -6363,6 +6425,8 @@ var StentorDirectChat = /** @class */ (function () {
                         if (origin) {
                             attributes["origin"] = origin;
                         }
+                        // A test lead from Studio's "send yourself a test lead" booking page
+                        addTestLeadAttribute_1(attributes);
                         // Add current time for accurate date/time responses
                         attributes["currentTime"] = new Date().toISOString();
                         now = new Date().getTime();
@@ -7591,6 +7655,8 @@ var StentorRouterChat = /** @class */ (function () {
                 if (origin) {
                     attributes["origin"] = origin;
                 }
+                // A test lead from Studio's "send yourself a test lead" booking page
+                addTestLeadAttribute_1(attributes);
                 // Add current time for accurate date/time responses
                 attributes["currentTime"] = new Date().toISOString();
                 request = requestFromMessage(message, userId, this.isNewSession, sessionId, accessToken, attributes, this.visitorInfo);
@@ -35900,8 +35966,17 @@ var MessageList = function (_a) {
     return (require$$0.jsxs("div", { className: "message-list-container", ref: containerRef, children: [require$$0.jsxs("div", { className: "message-list-container__msgs", children: [renderAll(), require$$0.jsx("div", { ref: messagesEndRef, style: { float: "left", clear: "both" } }), require$$0.jsx(QueuePosition, { position: queuePosition }), require$$0.jsx(TypingStatus, { agents: agents, textTypingStatusEnabled: textTypingStatusEnabled })] }), require$$0.jsx(ChatChipsContainer, {})] }));
 };
 
+/**
+ * Shown when a chat request never reached the server -- see `isTransportFailure`.
+ *
+ * This overlay covers the conversation, so its two lines are the only thing the visitor sees. It
+ * used to appear for every failure and say "Server is offline", which on 2026-09-25 was put in
+ * front of every visitor by a 500 from a server that was up and serving. The copy is now limited to
+ * what a failed request actually proves -- we could not reach it -- and names the one thing a
+ * visitor can do about it.
+ */
 var ServerOffline = function () {
-    return (require$$0.jsxs("div", { className: "server-offline", children: [require$$0.jsx("h2", { children: "Chat is currently unavailable" }), require$$0.jsx("h3", { children: "Server is offline" })] }));
+    return (require$$0.jsxs("div", { className: "server-offline", children: [require$$0.jsx("h2", { children: "We can't reach the chat right now" }), require$$0.jsx("h3", { children: "Check your connection and try again in a moment." })] }));
 };
 
 /**