@eshal-bot/chat-widget 0.1.38 → 0.1.39

package/dist/chat-widget.js

@@ -56008,21 +56008,22 @@
     // {category} placeholder is substituted at the call site (no i18n
     // interpolation engine here). Rendered through ReactMarkdown so the
     // **bold** segment comes out bold.
-    // Original was
-    //   "Sure! Here are the main topics under **{category}**. Pick one or
-    //    type your question below."
-    // referring to a tag-chip picker (TagSelectorInline) that's been off
-    // since EV-901 (SHOW_TAG_SELECTOR_BAR = false in ChatWindow.jsx).
-    // With no tag picker rendered, "Pick one" dangled — there was
-    // literally nothing to pick. Updated to drop the tag hint and tell
-    // the user to ask their question directly; the category filter
-    // already constrains RAG to the right corner of the knowledge base.
-    // (The widget doesn't currently call this string itself — the
-    // mirror in frontend/src/lib/i18n/widgetI18n.js is the active
-    // copy used by the Testing Lab + chatbot-preview. Kept in sync
-    // here so a future widget-side renderer doesn't ship the stale
-    // copy.)
-    categoryTopicsHeading: "Sure — ask anything about **{category}** and I'll answer using only what's published under that topic.",
+    //
+    // Copy history:
+    //   v1 — "Sure! Here are the main topics under **{category}**. Pick
+    //        one or type your question below." (referenced the
+    //        TagSelectorInline tag-chip picker; off since EV-901).
+    //   v2 — "Sure — ask anything about **{category}** and I'll answer
+    //        using only what's published under that topic." (after the
+    //        tag picker was hidden — explained the scoped behaviour).
+    //   v3 (current) — "Please ask your **{category}** question below."
+    //        (user feedback 2026-05-29: shorter + friendlier; category
+    //        scope is now implicit from the picker UI affordance).
+    //
+    // Kept in sync with frontend/src/lib/i18n/widgetI18n.js (the active
+    // copy used by the Testing Lab + chatbot-preview) so a future
+    // widget-side renderer doesn't ship a stale string.
+    categoryTopicsHeading: "Please ask your **{category}** question below.",
     // Heading shown above the initial-state quick-questions list, in
     // parallel with the category picker's "Choose a topic to get started:".
     quickQuestionsHeadingLabel: "Or ask a quick question:",
@@ -59383,6 +59384,7 @@
     (activeCategory === null || activeCategory === void 0 ? void 0 : activeCategory.tags) || [];
     const handleSelectCategory = reactExports.useCallback(categoryId => {
       if (!onWidgetFilterChange) return;
+      const prevId = (widgetFilter === null || widgetFilter === void 0 ? void 0 : widgetFilter.category) || null;
       if (!categoryId) {
         onWidgetFilterChange(null);
         return;
@@ -59393,16 +59395,22 @@
       });
       setCategoryPickUserMsgCount(userMessageCount);
 
-      // EV-901: single click = single answer. Send the category label
-      // as a user inquiry so the bot responds directly, instead of the
-      // old two-step flow that synthesized a "here are sub-topics" stub
-      // and waited for the user to pick a sub-tag.
-      if (onDirectSend) {
+      // Initial-state pick: inject a localized assistant ack bubble
+      // ("Please ask your **{category}** question below.") to mirror
+      // the testing-lab / chatbot-preview behaviour (InlineChat.tsx).
+      // Mid-conversation switches stay silent — the top CategoryTabsBar
+      // is enough affordance there. Same-chip re-tap is a no-op too.
+      // Replaces any prior ack bubble so switching categories shows
+      // ONE bubble at a time, not a growing stack.
+      if (!hasUserMessages && categoryId !== prevId && onSynthesizeAssistantMessage) {
         const cat = (filterCategories || []).find(c => c.id === categoryId);
         const label = (cat === null || cat === void 0 ? void 0 : cat.label) || categoryId;
-        onDirectSend(label);
+        const heading = t("categoryTopicsHeading").replace("{category}", label);
+        onSynthesizeAssistantMessage(heading, {
+          replaceMarker: "category-intro"
+        });
       }
-    }, [onWidgetFilterChange, userMessageCount, filterCategories, onDirectSend]);
+    }, [onWidgetFilterChange, widgetFilter, userMessageCount, filterCategories, hasUserMessages, onSynthesizeAssistantMessage, t]);
     reactExports.useCallback(tag => {
       const categoryId = (widgetFilter === null || widgetFilter === void 0 ? void 0 : widgetFilter.category) || (activeCategory === null || activeCategory === void 0 ? void 0 : activeCategory.id);
       if (categoryId && onWidgetFilterChange) {
@@ -59433,8 +59441,13 @@
 
     // QuickQuestions are hidden when the bottom slot is occupied by the
     // tag selector — the user explicitly asked for tag pills to take the
-    // place of QQ on the initial screen.
-    const shouldShowQuickQuestions = !hasUserMessages && quickQuestions.length > 0 && quickQuestionsEnabled && !showTagSelector;
+    // place of QQ on the initial screen. Also hidden once a category is
+    // picked in the initial state: the category-intro ack bubble
+    // ("Please ask your X question below.") explicitly cues the user to
+    // type their question, so showing conversation-starter chips
+    // underneath would contradict that affordance — matches the
+    // chatbot-preview behaviour.
+    const shouldShowQuickQuestions = !hasUserMessages && quickQuestions.length > 0 && quickQuestionsEnabled && !showTagSelector && !(widgetFilter !== null && widgetFilter !== void 0 && widgetFilter.category);
     const hasOnboardingQuestions = onboardingQuestions && onboardingQuestions.length > 0;
     const isCsatEnabled = Boolean(csatEnabled);
     const shouldHideResolveForOnboarding = onboardingEnabled && hasOnboardingQuestions && !onboardingCompleted;