Rich toast: thread / invite quick-reply misroutes (reply target is the coalescing tag, not a room id) #17

New Issue

2026-09-17T23:24:13-04:00

jared commented

2026-09-17 23:24:13 -04:00

Migrated from LOTUS_TODO.md on 2026-09-17 (the file is now reference-only).

[Med] [desktop] Thread / invite quick-reply misroutes. The reply target is the coalescing tag — ${roomId}:${threadId} for thread replies, 'lotus-invites' for invites (ClientNonUIFeatures.tsx:471,192) — not a real room id, so mx.sendMessage(tag, …) fails silently (useTauriToastActions.ts:37). Body-click navigation is correct (uses path). Fix: pass the real roomId separately (e.g. data.roomId) and have the shim (lib.rs NOTIFICATION_BRIDGE) + toast.rs use it for the reply target; keep tag for coalescing. Invite toasts should also drop the reply box (nothing to reply to).

_Migrated from `LOTUS_TODO.md` on 2026-09-17 (the file is now reference-only)._ **[Med] [desktop]** **Thread / invite quick-reply misroutes.** The reply target is the coalescing `tag` — `${roomId}:${threadId}` for thread replies, `'lotus-invites'` for invites (`ClientNonUIFeatures.tsx:471,192`) — not a real room id, so `mx.sendMessage(tag, …)` fails silently (`useTauriToastActions.ts:37`). Body-click navigation is correct (uses `path`). Fix: pass the real `roomId` separately (e.g. `data.roomId`) and have the shim (`lib.rs` `NOTIFICATION_BRIDGE`) + `toast.rs` use it for the reply target; keep `tag` for coalescing. Invite toasts should also drop the reply box (nothing to reply to).

jared added this to the Desktop 2026-Q4 milestone 2026-09-17 23:24:13 -04:00

jared added the bug priority: medium area: native labels 2026-09-17 23:24:13 -04:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: LotusGuild/cinny-desktop#17