@moveo-ai/web-client 0.114.0 → 0.115.1-true.1

package/README.md

@@ -197,6 +197,13 @@ Any other key passes through as a widget-config override for the loaded integrat
 | `setLocale(locale)`           | Switches the widget language                                 |
 | `destroy()`                   | Removes the widget from the page                             |
 
+`updateContext` calls made inside a 300 ms window merge into one update, so a
+burst of calls costs one round trip and the first call still ships at once.
+Arrays such as `tags` replace the stored value rather than append, so
+`tags: []` clears them. A call made before a conversation exists is held and
+sent once the session opens. `closeConversation` sends any update still queued
+before it ends the session.
+
 ### WidgetController Events
 
 Register a callback per event. Every callback returns nothing and receives the
@@ -223,6 +230,8 @@ a message — never carries the text), `launcher_clicked`,
 `teaser_quick_reply_clicked` (a teaser reply the visitor tapped, carrying its
 configured `label`), `teaser_composer_submitted` (the visitor sent their own
 line from the teaser — carries no properties, because the text is theirs),
+`section_not_found` (a `teaser.pages[].sections[]` entry whose strongest
+selector no longer matches the page — see "A different teaser per section"),
 `rating_submitted`, and the rest of the `AnalyticsEvent` enum in
 `src/hooks/useAnalytics.ts`.
 
@@ -415,6 +424,93 @@ the new URL, and the teaser re-resolves. An integration that configures no
 `pages[]` is not watched at all, because the watcher patches `history` and never
 restores it.
 
+#### A different teaser per section of a page
+
+On a long page one teaser is one teaser for fourteen blocks. `sections[]`, nested
+in a `pages[]` entry, gives each part of the page its own, and the teaser
+follows what the visitor is reading.
+
+```javascript
+MoveoAI.init({
+  integrationId: 'YOUR_INTEGRATION_ID',
+  teaser: {
+    quick_replies: ['Compare products', 'Help me choose'],
+    pages: [
+      {
+        url: '/shop',
+        id: 'shop',
+        quick_replies: ['Which Clover system fits my business?'],
+        sections: [
+          {
+            id: 'station_duo',
+            match: [
+              '[data-entry-id="3UlHnDQQTGvNwHKQnXgVTz"]',
+              'article > section:nth-of-type(6)',
+            ],
+            quick_replies: [
+              'Is Station Duo worth $1,899?',
+              'Station Duo or Flex?',
+            ],
+          },
+          {
+            id: 'go',
+            match: ['[data-entry-id="5oA3X1sZOG6FGGUrk39jiR"]'],
+            quick_replies: ['Does Go work without a counter?'],
+          },
+          { id: 'legal', match: ['#legal'], variant: 'none' },
+        ],
+      },
+    ],
+  },
+});
+```
+
+**Resolution is section → page → block.** The section in view wins; no section
+in view falls back to the page's teaser; no page match falls back to the block.
+A section set to `variant: 'none'` goes quiet and does **not** fall back — it is
+an instruction, not an absence.
+
+**`match` is an ordered list of CSS selectors, strongest first**, and nothing
+else: the loader runs `querySelector` on each until one matches, and observes
+that element. A selector matching several elements resolves to the first in
+document order. Put a stable `id` or a CMS data attribute first and a positional
+selector like `article > section:nth-of-type(6)` last, so a section survives
+losing its best anchor. Hashed CSS-module class names change on every deploy;
+never use one.
+
+**`id` is authored, not derived from position.** It names the section in
+analytics, so an index that shifted whenever someone reordered the list would
+break the history. Unlike `pages[]`, the order of `sections[]` decides nothing:
+sections are chosen at runtime by what is on screen.
+
+**The section with the largest visible share of the viewport wins**, not the
+one with the largest visible ratio of itself — a 992px section 40% in view
+fills more screen than a 373px one fully in view. A tie keeps the current
+section, so a slow scroll cannot flap between two sets of chips, and a section
+must hold the viewport for a moment before the teaser follows it, so one flick
+of the wheel does not fire three swaps. The swap lands while the teaser is out
+of the way for the scroll, and the new chips are what fades back in.
+
+**`show_after` gates the first show only.** A later swap never waits — a visitor
+scanning a long page would otherwise restart the delay at every block and see
+nothing. **A new section re-arms a teaser that `hide_after` retired**, with a
+fresh budget. **A teaser the visitor closed stays closed** for the visit,
+whatever section they reach.
+
+**Sections belong to their page.** A single-page-app navigation rebuilds the
+watch against the new page's sections, and clears the current section so
+nothing from the previous page survives the transition. A page with no
+`sections[]`, or an empty list, is not observed at all, and an integration
+with no sections anywhere registers no observer.
+
+**When a selector stops matching**, the widget emits the `section_not_found`
+analytics event once per section per page view, carrying `section_id`,
+`page_id`, `page_url`, `matched_index` and `selector_count`. It fires whenever
+the strongest selector no longer holds: `matched_index` names the fallback that
+still does, so the section can be regenerated before it breaks, and is `null`
+once nothing matches. A section with no match is simply left out of the
+running; the page teaser covers it.
+
 **Chips replace the line, they do not sit under it.** Asking the question and
 offering the answers says the same thing twice, and a bubble above
 content-width chips leaves a ragged edge.
@@ -652,14 +748,14 @@ icon and the launcher, and `--color-chat-background` follows the background.
 Six more colours have no `theme_colors` key, so they are set through
 `setCSSVariables()` only:
 
-| Variable                             | Controls                                                            |
-| ------------------------------------ | ------------------------------------------------------------------- |
-| `--color-chat-background`            | The area behind the messages; follows the background                |
-| `--color-options-background`         | Quick reply buttons, and the teaser chips and composer field        |
-| `--color-options-foreground`         | Quick reply labels, the teaser composer text, and a chip under the pointer or the focus ring; defaults to the accent |
+| Variable                             | Controls                                                                                                               |
+| ------------------------------------ | ---------------------------------------------------------------------------------------------------------------------- |
+| `--color-chat-background`            | The area behind the messages; follows the background                                                                   |
+| `--color-options-background`         | Quick reply buttons, and the teaser chips and composer field                                                           |
+| `--color-options-foreground`         | Quick reply labels, the teaser composer text, and a chip under the pointer or the focus ring; defaults to the accent   |
 | `--color-options-border`             | Quick reply borders, the teaser composer field, and a chip under the pointer or the focus ring; defaults to the accent |
-| `--color-opening-message-background` | The teaser bubble, on `callout` and `composer`; defaults to the accent |
-| `--color-opening-message-foreground` | The teaser bubble text; defaults to the visitor's own bubble text colour |
+| `--color-opening-message-background` | The teaser bubble, on `callout` and `composer`; defaults to the accent                                                 |
+| `--color-opening-message-foreground` | The teaser bubble text; defaults to the visitor's own bubble text colour                                               |
 
 The two `opening-message` names are the teaser's, from before it was called
 one. They are the only lever that moves the bubble off the accent, so an

package/dist/63.min.js.LICENSE.txt

@@ -1,6 +1,6 @@
 /*!
  * 
- *   @moveo-ai/web-client v0.114.0
+ *   @moveo-ai/web-client v0.115.1-true.1
  *   Copyright (c) Moveo.ai (TM)
  *
  */

package/dist/752.min.js.LICENSE.txt

@@ -1,6 +1,6 @@
 /*!
  * 
- *   @moveo-ai/web-client v0.114.0
+ *   @moveo-ai/web-client v0.115.1-true.1
  *   Copyright (c) Moveo.ai (TM)
  *
  */

package/dist/882.min.js.LICENSE.txt

@@ -1,6 +1,6 @@
 /*!
  * 
- *   @moveo-ai/web-client v0.114.0
+ *   @moveo-ai/web-client v0.115.1-true.1
  *   Copyright (c) Moveo.ai (TM)
  *
  */

package/dist/929.min.js.LICENSE.txt

@@ -1,6 +1,6 @@
 /*!
  * 
- *   @moveo-ai/web-client v0.114.0
+ *   @moveo-ai/web-client v0.115.1-true.1
  *   Copyright (c) Moveo.ai (TM)
  *
  */