@moveo-ai/web-client 0.110.0-true.9 → 0.110.1-true.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +36 -21
- package/dist/63.min.js.LICENSE.txt +1 -1
- package/dist/752.min.js.LICENSE.txt +1 -1
- package/dist/882.min.js.LICENSE.txt +1 -1
- package/dist/929.min.js.LICENSE.txt +1 -1
- package/dist/audio-client.min.js.LICENSE.txt +1 -1
- package/dist/iframe.min.js +1 -1
- package/dist/iframe.min.js.LICENSE.txt +1 -1
- package/dist/index.html +1 -1
- package/dist/preview/index.html +2 -2
- package/dist/preview.css.min.js.LICENSE.txt +1 -1
- package/dist/telnyx-client.min.js.LICENSE.txt +1 -1
- package/dist/web-client.min.js.LICENSE.txt +1 -1
- package/dist/webrtc-client.min.js.LICENSE.txt +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -229,25 +229,36 @@ callback at any time — a callback added after the widget loaded still receives
|
|
|
229
229
|
`widget_loaded` on registration, so the event cannot be missed in the race
|
|
230
230
|
between `init()` resolving and your `.then()` running.
|
|
231
231
|
|
|
232
|
-
####
|
|
233
|
-
|
|
234
|
-
|
|
235
|
-
|
|
236
|
-
|
|
237
|
-
|
|
238
|
-
|
|
239
|
-
|
|
240
|
-
|
|
241
|
-
|
|
242
|
-
|
|
243
|
-
|
|
244
|
-
|
|
245
|
-
|
|
246
|
-
|
|
247
|
-
|
|
248
|
-
|
|
249
|
-
|
|
250
|
-
|
|
232
|
+
#### How the header controls end a conversation
|
|
233
|
+
|
|
234
|
+
Two header controls can end a conversation, and they report differently.
|
|
235
|
+
|
|
236
|
+
**The close button (X)** asks first. Once the conversation has messages, it
|
|
237
|
+
opens a confirmation offering **End conversation** and **Minimize**. Ending
|
|
238
|
+
runs the end-of-chat survey when the account has one. On an empty chat, or
|
|
239
|
+
while a prompt or webview owns the panel, it just hides the panel. Set
|
|
240
|
+
`close_minimizes_window: true` and the button always minimizes and never ends.
|
|
241
|
+
|
|
242
|
+
**Restart**, in the header title menu, does not ask. It ends the conversation
|
|
243
|
+
and opens the next one in place, with the panel still open, and shows no
|
|
244
|
+
end-of-chat survey.
|
|
245
|
+
|
|
246
|
+
During a voice call the close button ends the call, after its own confirmation.
|
|
247
|
+
|
|
248
|
+
Which event to count:
|
|
249
|
+
|
|
250
|
+
| Event | Fires when | Means the conversation ended |
|
|
251
|
+
| ----------------------------------- | ---------------------------------------------------------- | ---------------------------- |
|
|
252
|
+
| `close_icon_clicked` | The visitor presses X, before they answer the confirmation | No |
|
|
253
|
+
| `popover_end_chat_clicked` | They confirm **End conversation** | Yes |
|
|
254
|
+
| `popover_end_chat_continue_clicked` | They pick **Minimize** instead | No |
|
|
255
|
+
| `restart_conversation_clicked` | They pick **Restart** from the menu | Yes |
|
|
256
|
+
|
|
257
|
+
Add `popover_end_chat_clicked` and `restart_conversation_clicked` for the
|
|
258
|
+
number of conversations visitors ended themselves. `close_icon_clicked` counts
|
|
259
|
+
presses, not conversations: count it as an end and you overstate your totals.
|
|
260
|
+
`onSessionClosed` covers the visitor-confirmed end, and `onConversationClosed`
|
|
261
|
+
covers a close that came from the agent side, so neither alone is a total.
|
|
251
262
|
|
|
252
263
|
### Forward widget events into your analytics
|
|
253
264
|
|
|
@@ -407,14 +418,18 @@ the supported surface.
|
|
|
407
418
|
#### Colours
|
|
408
419
|
|
|
409
420
|
Set colours in the integration's `theme_colors` config, which carries a `light`
|
|
410
|
-
and a `dark` set. Each key writes
|
|
411
|
-
overridden at runtime through `setCSSVariables()`, which wins
|
|
421
|
+
and a `dark` set. Each key writes the CSS variables listed below, so the same
|
|
422
|
+
colours can be overridden at runtime through `setCSSVariables()`, which wins
|
|
423
|
+
over the config. `border_color` is the one key that writes two: control
|
|
424
|
+
boundaries need their own token to stay above the 3:1 WCAG 1.4.11 asks of them,
|
|
425
|
+
while dividers and card edges stay lighter.
|
|
412
426
|
|
|
413
427
|
| `theme_colors` key | CSS variable | Controls |
|
|
414
428
|
| ---------------------- | ----------------------------------- | ----------------------------------------------------------- |
|
|
415
429
|
| `accent_color` | `--color-accent` | The accent, and the default for every colour marked below |
|
|
416
430
|
| `background_color` | `--color-background` | The widget surface, and the area behind the messages |
|
|
417
431
|
| `border_color` | `--color-border` | Panel, composer and card borders |
|
|
432
|
+
| `border_color` | `--color-stroke-input` | Form controls, outline buttons, file links, carousel dots |
|
|
418
433
|
| `header_color` | `--moveo-header-background` | Header background |
|
|
419
434
|
| `text_color_header` | `--moveo-header-text-color` | Header text and icons |
|
|
420
435
|
| `text_color_user` | `--color-text-primary-foreground` | Text inside the visitor's own bubbles |
|