Software /
code /
prosody
File
spec/scansion/muc_subject_issue_667.scs @ 12745:2cbf0e9314ff
mod_smacks: Change boolean attribute from '1' to 'true' for compatibility
Conversations 2.10.10 and earlier expect this to be literally 'true' and don't
recognise '1'. This leads to it not attempting resumption with Prosody at all
since this change was introduced in 36ba170c4fd0.
Thanks to Zash for noticing, debugging and diagnosing this issue.
This issue is fixed in Conversations commit 052c58f3 (unreleased at the time
of writing).
author | Matthew Wild <mwild1@gmail.com> |
---|---|
date | Fri, 07 Oct 2022 11:35:56 +0100 |
parent | 9708:6507df6d2c55 |
child | 13414:d54364746a7c |
line wrap: on
line source
# #667 MUC message with subject and body SHALL NOT be interpreted as a subject change [Client] Romeo password: password jid: romeo@localhost ----- Romeo connects # and creates a room Romeo sends: <presence to="issue667@conference.localhost/Romeo"> <x xmlns="http://jabber.org/protocol/muc"/> </presence> Romeo receives: <presence from="issue667@conference.localhost/Romeo"> <x xmlns="http://jabber.org/protocol/muc#user"> <status code="201"/> <item affiliation="owner" role="moderator" jid="${Romeo's full JID}"/> <status code="110"/> </x> </presence> # the default (empty) subject Romeo receives: <message type="groupchat" from="issue667@conference.localhost"> <subject/> </message> # this should be treated as a normal message Romeo sends: <message to="issue667@conference.localhost" type="groupchat"> <subject>Greetings</subject> <body>Hello everyone</body> </message> Romeo receives: <message type="groupchat" from="issue667@conference.localhost/Romeo"> <subject>Greetings</subject> <body>Hello everyone</body> </message> # Resync Romeo sends: <presence to="issue667@conference.localhost/Romeo"> <x xmlns="http://jabber.org/protocol/muc"/> </presence> # Presences Romeo receives: <presence from="issue667@conference.localhost/Romeo"> <x xmlns="http://jabber.org/protocol/muc#user"> <item affiliation="owner" role="moderator" jid="${Romeo's full JID}"/> <status code="110"/> </x> </presence> Romeo receives: <message type="groupchat" from="issue667@conference.localhost/Romeo"> <subject>Greetings</subject> <body>Hello everyone</body> </message> # the still empty subject Romeo receives: <message type="groupchat" from="issue667@conference.localhost"> <subject/> </message> # this is a subject change Romeo sends: <message to="issue667@conference.localhost" type="groupchat"> <subject>Something to talk about</subject> </message> Romeo receives: <message type="groupchat" from="issue667@conference.localhost/Romeo"> <subject>Something to talk about</subject> </message> # a message without <subject> Romeo sends: <message to="issue667@conference.localhost" type="groupchat"> <body>Lorem ipsum dolor sit amet</body> </message> Romeo receives: <message type="groupchat" from="issue667@conference.localhost/Romeo"> <body>Lorem ipsum dolor sit amet</body> </message> # Resync Romeo sends: <presence to="issue667@conference.localhost/Romeo"> <x xmlns="http://jabber.org/protocol/muc"/> </presence> # Presences Romeo receives: <presence from="issue667@conference.localhost/Romeo"> <x xmlns="http://jabber.org/protocol/muc#user"> <item affiliation="owner" role="moderator" jid="${Romeo's full JID}"/> <status code="110"/> </x> </presence> # History # These have delay tags but we ignore those for now Romeo receives: <message type="groupchat" from="issue667@conference.localhost/Romeo"> <subject>Greetings</subject> <body>Hello everyone</body> </message> Romeo receives: <message type="groupchat" from="issue667@conference.localhost/Romeo"> <body>Lorem ipsum dolor sit amet</body> </message> # Finally, the topic Romeo receives: <message type="groupchat" from="issue667@conference.localhost/Romeo"> <subject>Something to talk about</subject> </message> Romeo disconnects