Skip to content

[chat] replyToId from XEP-0461 is parsed in lib-jitsi-meet but dropped in middleware before reaching Redux state #17196

@Alok-work23

Description

@Alok-work23

What problem are you trying to solve?

XEP-0461 (Message Replies) support was added to
lib-jitsi-meet in PR #2922. _parseReplyMessage()
correctly extracts replyToId from incoming stanzas
and JitsiConferenceEventManager forwards it as the
last argument of MESSAGE_RECEIVED and
PRIVATE_MESSAGE_RECEIVED events.

However _addChatMsgListener() in middleware.ts
in jitsi-meet never captures this argument — it is
silently dropped before reaching Redux state or the UI.

This means despite lib-jitsi-meet fully supporting
XEP-0461, the reply metadata never reaches the
React/Redux layer, making it impossible to display
threaded reply UI.

What solution would you like to see?

replyToId should be captured and stored as
replyToMessageId in Redux state so the UI layer
can use it to display reply context.

Is there an alternative?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature-requestIssue which suggest an idea, enhancement or feature to implement

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions