Chat list shows a room JID fragment instead of the group name #24

Closed
opened 2026-11-06 09:00:11 +00:00 by asemeniv · 1 comment
Member

Chat list shows a room JID fragment instead of the group name
Problem
When a room bookmark has an empty name, the chat list and the group header use different fallback logic.

The group header displays the actual room name, while the chat list displays the part of the room JID before @.

Preconditions
User testman421 is a member of “New 86 14102026 1”.
The room bookmark received from the server has an empty name: "name": "".
Steps to reproduce
Open the Chats tab on iPhone 13.
Find the group “New 86 14102026 1”.
Open the group and check its header.
Actual result
Chat list: qlwhfw7f7fue
Group header: New 86 1410…
Expected result
The chat list and group header should display the same group name.

Suggested direction
Use the room name as a fallback when the bookmark name is empty, rather than displaying a fragment of the room JID.

Note: The requirements specification confirms that a MUC has a name but does not explicitly define how it should be displayed. This issue is therefore a recommendation for consistent UI behavior.

Chat list shows a room JID fragment instead of the group name Problem When a room bookmark has an empty name, the chat list and the group header use different fallback logic. The group header displays the actual room name, while the chat list displays the part of the room JID before @. Preconditions User testman421 is a member of “New 86 14102026 1”. The room bookmark received from the server has an empty name: "name": "". Steps to reproduce Open the Chats tab on iPhone 13. Find the group “New 86 14102026 1”. Open the group and check its header. Actual result Chat list: qlwhfw7f7fue Group header: New 86 1410… Expected result The chat list and group header should display the same group name. Suggested direction Use the room name as a fallback when the bookmark name is empty, rather than displaying a fragment of the room JID. Note: The requirements specification confirms that a MUC has a name but does not explicitly define how it should be displayed. This issue is therefore a recommendation for consistent UI behavior.
Contributor

Moved to another-im/libtacky#21 with the analysis of the cause and a proposed fix: it is libtacky's to change. Closing here.

Moved to another-im/libtacky#21 with the analysis of the cause and a proposed fix: it is libtacky's to change. Closing here.
fmodf closed this issue 2026-11-07 08:55:20 +00:00
Sign in to join this conversation.
No labels
done
fixed
returned
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
another-im/anotherim-swift#24
No description provided.