@ethora/chat-component 26.6.7 → 26.7.2

package/dist/networking/authRefresh.d.ts

@@ -1,3 +1,4 @@
+import { User } from '../types/types';
 /**
  * THE single refresh-token rotation point for the SDK.
  *
@@ -98,5 +99,10 @@ export declare function refreshAuthTokens(options?: RefreshOptions): Promise<Ref
  */
 export declare function refreshAuthTokensQuietly(): Promise<RefreshResult | null>;
 export declare function startCrossTabTokenSync(): () => void;
+type CredentialLike = Partial<Pick<User, 'xmppUsername' | 'refreshToken' | 'token'>> | null | undefined;
+export declare function markCurrentSessionDead(): void;
+export declare function isSessionDead(candidate: CredentialLike): boolean;
+export declare function clearDeadSessionLatch(): void;
 /** Test seam: drops any shared in-flight promise between cases. */
 export declare function __resetAuthRefreshStateForTests(): void;
+export {};

package/dist/networking/xmppClient.d.ts

@@ -22,6 +22,7 @@ export declare class XmppClient implements XmppClientInterface {
     private reconnecting;
     private reconnectPromise;
     presencesReady: boolean;
+    private sendAllPresencesInFlight;
     private connectionSteps;
     private messageQueue;
     private highLaneBurstLimit;
@@ -141,6 +142,7 @@ export declare class XmppClient implements XmppClientInterface {
     private startAdaptivePing;
     private markActivity;
     sendAllPresencesAndMarkReady(): Promise<void>;
+    private runAllPresencesSweep;
     reconnect(): Promise<void>;
     allRoomPresencesStanza(): Promise<AllRoomPresenceSummary>;
     ensureConnected(timeout?: number): Promise<void>;

package/dist/roomStore/Middleware/unreadMidlleware.d.ts

@@ -1,2 +1,3 @@
 import { Middleware } from '@reduxjs/toolkit';
+export declare const resolveTouchedRooms: (action: any, prevState: any, nextState: any) => Set<string>;
 export declare const unreadMiddleware: Middleware;

package/dist/roomStore/callSlice.d.ts

@@ -13,6 +13,7 @@ export interface CallState {
     token: string | null;
     error: string | null;
     startedAt: number | null;
+    connectedAt: number | null;
 }
 export declare const startOutgoingCall: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<{
     roomJid: string;

package/dist/roomStore/chatSettingsSlice.d.ts

@@ -8,6 +8,30 @@ interface ChatState {
     selectedUser?: IUser;
     activeFile?: ModalFile;
     langSource?: Iso639_1Codes;
+    /**
+     * Whether THIS reader's own outgoing messages get tagged with
+     * `<translate source="xx"/>` (see sendTextMessageWithTranslateTag) so
+     * translations can be generated for them. Defaults to true so existing
+     * hosts that already set `config.translates.enabled` see no change
+     * until a reader explicitly opts out via the language-selector toggle.
+     *
+     * Turning this off does NOT untag anything already sent - a message
+     * ships with whatever tag was active at send time, permanently. Turning
+     * it back on only affects messages sent from that point forward. Same
+     * asymmetry the other direction: turning it on doesn't retroactively
+     * tag old messages either - see the disclaimer surfaced next to the
+     * toggle in LanguageSelectorModal.
+     */
+    translateSendEnabled?: boolean;
+    /**
+     * Reader's own auto/manual pick from the language-selector modal's
+     * switcher. Undefined means "never touched it" - falls back to
+     * `config.translates.mode` (see resolveTranslateMode). Ignored entirely
+     * when the host sets `config.translates.forceType: true`, which is also
+     * why the switcher itself doesn't render in that case - nothing should
+     * ever write here that a host has pinned.
+     */
+    translateMode?: 'auto' | 'manual';
 }
 export declare const setUser: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<User, "chatSettingStore/setUser">, setConfig: import('@reduxjs/toolkit').ActionCreatorWithNonInferrablePayload<"chatSettingStore/setConfig">, refreshTokens: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<{
     token: string;
@@ -16,6 +40,6 @@ export declare const setUser: import('@reduxjs/toolkit').ActionCreatorWithOption
     xmppPassword?: string;
 }, "chatSettingStore/refreshTokens">, logout: import('@reduxjs/toolkit').ActionCreatorWithoutPayload<"chatSettingStore/logout">, setActiveModal: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<string, "chatSettingStore/setActiveModal">, setDeleteModal: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<DeleteModal, "chatSettingStore/setDeleteModal">, setSelectedUser: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<IUser, "chatSettingStore/setSelectedUser">, updateUser: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<{
     updates: Partial<User>;
-}, "chatSettingStore/updateUser">, setActiveFile: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<ModalFile, "chatSettingStore/setActiveFile">, setLangSource: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<Iso639_1Codes, "chatSettingStore/setLangSource">;
+}, "chatSettingStore/updateUser">, setActiveFile: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<ModalFile, "chatSettingStore/setActiveFile">, setLangSource: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<Iso639_1Codes, "chatSettingStore/setLangSource">, setTranslateSendEnabled: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<boolean, "chatSettingStore/setTranslateSendEnabled">, setTranslateMode: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<"auto" | "manual", "chatSettingStore/setTranslateMode">;
 declare const _default: import('redux').Reducer<ChatState>;
 export default _default;

package/dist/roomStore/roomsSlice.d.ts

@@ -9,6 +9,7 @@ interface RoomMessagesState {
     editAction?: EditAction;
     isLoading: boolean;
     usersSet: Record<string, RoomMember>;
+    presenceByRoom: Record<string, string[]>;
     reportRoom: {
         isOpen: boolean;
     };
@@ -67,7 +68,13 @@ export declare const addRoom: import('@reduxjs/toolkit').ActionCreatorWithOption
     chatJID?: string;
 }, "roomMessages/setRoomNoMessages">, setCurrentRoom: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<{
     roomJID: string | null;
-}, "roomMessages/setCurrentRoom">, setChatUiVisible: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<boolean, "roomMessages/setChatUiVisible">, setRoomRole: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<{
+}, "roomMessages/setCurrentRoom">, setMemberOnline: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<{
+    roomJID: string;
+    xmppUsername: string;
+}, "roomMessages/setMemberOnline">, setMemberOffline: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<{
+    roomJID: string;
+    xmppUsername: string;
+}, "roomMessages/setMemberOffline">, setChatUiVisible: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<boolean, "roomMessages/setChatUiVisible">, setRoomRole: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<{
     chatJID: string;
     role: string;
 }, "roomMessages/setRoomRole">, setReactions: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<ReactionAction, "roomMessages/setReactions">, setLogoutState: import('@reduxjs/toolkit').ActionCreatorWithoutPayload<"roomMessages/setLogoutState">, setActiveMessage: import('@reduxjs/toolkit').ActionCreatorWithOptionalPayload<{

package/dist/types/models/config.model.d.ts

@@ -238,6 +238,88 @@ export interface IConfig {
     translates?: {
         enabled: boolean;
         translations?: Iso639_1Codes;
+        /**
+         * 'auto' shows the translation inline automatically. 'manual' shows a
+         * "Translate" link the reader clicks (LinkedIn-style), then renders the
+         * result inline with a "Show original" toggle. Default 'auto'.
+         *
+         * Neither mode calls any translation service - both only ever display
+         * `message.translations`, whatever arrived attached to the stanza (see
+         * `readerLocale` below for how a message gets translated in the first
+         * place). This is purely a display choice: show it immediately, or let
+         * the reader ask for it.
+         */
+        mode?: 'auto' | 'manual';
+        /**
+         * Pins `mode` as fixed host policy. When true, the language-selector
+         * modal's auto/manual switcher does not render at all, and the reader
+         * has no way to override `mode` - it's always whatever the host set.
+         * Defaults to false: the reader can flip between auto and manual
+         * themselves via the switcher, which then wins over `mode` (the host's
+         * declared default, used until the reader touches it).
+         */
+        forceType?: boolean;
+        /**
+         * Reader's full locale (BCP-47, e.g. "fr-CA"). Falls back to
+         * `config.i18n.locale`. The region is passed through to `onTranslate` so
+         * the service can distinguish fr-CA vs fr-FR; the Translate button
+         * visibility comparison ignores the region (en-US vs en-CA => no button).
+         *
+         * This is also how a host drives the reader's language from OUTSIDE the
+         * chat component: set it (e.g. from your own app's language switcher)
+         * and pass the updated config down as a normal prop. Whenever it
+         * changes, the component syncs it into the same internal state the
+         * in-chat language picker writes to - so it drives both what a reader
+         * sees translated INTO and the source language declared on their own
+         * outgoing messages. Leave unset to let the reader manage it themselves
+         * via the picker (see `showLanguageSelector`).
+         */
+        readerLocale?: string;
+        /**
+         * Shows/hides the globe-icon language picker in the chat header.
+         * Defaults to true whenever `enabled` is true. Set to false when the
+         * host manages the reader's language itself (via `readerLocale`) and
+         * an in-chat picker would just be a second, redundant control.
+         */
+        showLanguageSelector?: boolean;
+        /**
+         * Shows/hides the list of selectable languages INSIDE the picker
+         * (English/Español/...). Defaults to true. Set to false to keep only
+         * the enable/disable-translates toggle - for hosts that drive the
+         * reader's language externally via `readerLocale` and don't want a
+         * second, redundant language list, but still want the reader to control
+         * whether their own outgoing messages get tagged for translation.
+         */
+        showLanguageList?: boolean;
+        /**
+         * Host-provided translation function. When set, the manual Translate
+         * action calls this - wire it to your own service - instead of reading
+         * `message.translations`. Optional; omit to use only what already
+         * arrived over XMPP.
+         */
+        onTranslate?: (text: string, ctx: {
+            sourceLocale?: string;
+            targetLocale: string;
+            message: IMessage;
+        }) => Promise<string>;
+        /**
+         * Host predicate deciding whether to show the Translate action for a given
+         * message. When omitted, the component compares base languages (message
+         * source vs reader, region ignored) and shows the action when they differ.
+         */
+        showTranslateForMessage?: (message: IMessage) => boolean;
+    };
+    /**
+     * Static UI i18n (interface captions like "Search...", "Type message").
+     * `locale` is a BCP-47 tag the host passes from the device/user (e.g. "en",
+     * "fr-CA", "es-US"); captions resolve to its base language. `strings`
+     * overrides or extends any built-in caption by key (see src/i18n/strings.ts).
+     * Built-in languages: en, fr, es. Independent from `translates` (dynamic
+     * per-message translation).
+     */
+    i18n?: {
+        locale?: string;
+        strings?: Record<string, string>;
     };
     disableRoomConfig?: boolean;
     disableProfilesInteractions?: boolean;
@@ -377,6 +459,46 @@ export interface IConfig {
         iconPath?: string;
         badgePath?: string;
         softAsk?: boolean;
+        /**
+         * In-app banner that nudges the user to turn on browser notifications.
+         * Off by default. The banner renders one of two states automatically from
+         * the current `Notification.permission`:
+         *  - "default" (never asked) → an "Enable notifications" card with a button
+         *    that triggers the browser permission prompt;
+         *  - "denied" (blocked) → a "Notifications are blocked" card explaining how
+         *    to re-allow it from the browser's site settings.
+         * It hides itself entirely once permission is "granted", when the browser
+         * has no Notification API, or when `pushNotifications.enabled` is not true.
+         * Every label is overridable so it can be localised.
+         */
+        permissionBanner?: {
+            /** Master switch for the banner. Default false (opt-in). */
+            enabled?: boolean;
+            /** Show the prompt while permission is "default". Default true. */
+            showWhenDefault?: boolean;
+            /**
+             * Show the notice while permission is "denied". Default false: a blocked
+             * state can only be fixed by hand in the browser's site settings, so by
+             * default we don't nag. Set true to opt back into the reminder.
+             */
+            showWhenBlocked?: boolean;
+            /** Render a dismiss (×) control. Default true. Dismissal lasts the tab session. */
+            dismissible?: boolean;
+            /** Where the fixed banner is anchored. Default "bottom-right". */
+            position?: 'top-left' | 'top-right' | 'top-center' | 'bottom-left' | 'bottom-right' | 'bottom-center';
+            /** Title for the "enable" state. Default "Enable notifications". */
+            enableTitle?: string;
+            /** Description for the "enable" state. */
+            enableDescription?: string;
+            /** Button label for the "enable" state. Default "Enable notifications". */
+            enableButtonLabel?: string;
+            /** Title for the "blocked" state. Default "Notifications are blocked". */
+            blockedTitle?: string;
+            /** Description for the "blocked" state. */
+            blockedDescription?: string;
+            /** Inline style overrides merged onto the banner container. */
+            style?: React.CSSProperties;
+        };
         onClick?: (params: {
             roomJID?: string;
             messageId?: string;

package/dist/types/models/language.model.d.ts

@@ -1,4 +1,4 @@
-export type Iso639_1Codes = 'en' | 'es' | 'pt' | 'ht' | 'zh';
+export type Iso639_1Codes = 'en' | 'en-CA' | 'es' | 'es-US' | 'pt' | 'ht' | 'fr' | 'fr-CA' | 'zh';
 export interface Language {
     iso639_1: Iso639_1Codes;
     name: string;

package/dist/types/models/message.model.d.ts

@@ -22,6 +22,7 @@ export interface IMessage {
     activeMessage?: boolean;
     isReply?: boolean | string;
     isDeleted?: boolean;
+    isEdited?: boolean;
     mainMessage?: string;
     reply?: IReply[];
     reaction?: Record<string, ReactionMessage>;

package/dist/utils/translateModePolicy.d.ts

@@ -0,0 +1,19 @@
+import { IConfig } from '../types/types';
+export type TranslateMode = 'auto' | 'manual';
+/**
+ * Whether the reader is allowed to pick auto vs manual themselves via the
+ * language-selector modal's switcher. `forceType: true` means the host has
+ * pinned `translates.mode` as policy - the switcher must not even render,
+ * let alone let a reader flip it.
+ */
+export declare const canReaderChooseTranslateMode: (translates?: IConfig["translates"]) => boolean;
+/**
+ * The mode actually in effect for this reader right now.
+ *
+ * `forceType` wins unconditionally - even a leftover `readerMode` from
+ * before the host turned forcing on must not leak through. Otherwise the
+ * reader's own pick (if they've touched the switcher) wins over the host's
+ * declared default, and the host's `mode` (defaulting to 'auto') is the
+ * fallback for a reader who never has.
+ */
+export declare const resolveTranslateMode: (translates?: IConfig["translates"], readerMode?: TranslateMode) => TranslateMode;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@ethora/chat-component",
-  "version": "26.6.7",
+  "version": "26.7.2",
   "type": "module",
   "main": "dist/main.js",
   "types": "dist/main.d.ts",

package/public/firebase-messaging-sw.js

@@ -384,9 +384,10 @@ async function handlePush(raw = {}, source = 'push') {
   });
 
   const visible = isVisibleClients(windowClients);
+  const hasAnyClient = windowClients.length > 0;
 
   if (DEBUG) log('clients:', dumpClients(windowClients));
-  log('visibleClientExists:', visible);
+  log('visibleClientExists:', visible, 'anyClientExists:', hasAnyClient);
 
   await broadcastDebugMessage({
     source,
@@ -445,9 +446,20 @@ async function handlePush(raw = {}, source = 'push') {
     },
   };
 
-  if (!visible) {
+  // Calls: a client that's merely backgrounded (open, just not the
+  // visible/focused tab) is NOT the "nobody will hear this ring" case -
+  // VideoCallOverlay already rings its own OS notification for exactly
+  // that state (see its comment: this SW push is meant to be the
+  // fully-offline fallback). `visible` collapses "backgrounded but open"
+  // and "fully closed" into the same false, which duplicated that
+  // client-side ring every time the tab was merely hidden. Suppress on
+  // ANY open client for calls; regular messages keep the visible-only
+  // check they already had.
+  const suppress = isCall ? hasAnyClient : visible;
+
+  if (!suppress) {
     log('SHOW NOTIFICATION', {
-      reason: 'NO_VISIBLE_CLIENT',
+      reason: isCall ? 'NO_CLIENT_AT_ALL' : 'NO_VISIBLE_CLIENT',
       tag: options.tag,
       isCall,
     });
@@ -456,7 +468,7 @@ async function handlePush(raw = {}, source = 'push') {
   }
 
   log('SKIP NOTIFICATION', {
-    reason: 'VISIBLE_CLIENT',
+    reason: isCall ? 'CLIENT_OPEN_WILL_RING_ITSELF' : 'VISIBLE_CLIENT',
   });
 }
 

package/dist/components/MessageBubble/MessageTranslations.d.ts

@@ -1,10 +0,0 @@
-import { FC } from 'react';
-import { IConfig, IMessage } from '../../types/types';
-interface MessageTranslationsProps {
-    message: IMessage;
-    langSource?: string;
-    isUser: boolean;
-    config?: IConfig;
-}
-declare const MessageTranslations: FC<MessageTranslationsProps>;
-export default MessageTranslations;