#667 MUC message with subject and body SHALL NOT be interpreted as a subject change
Please provide a snippet of the part of the specification which we violate
The subject is changed by sending a message of type "groupchat" to the <room@service>, where the <message/> MUST contain a <subject/> element that specifies the new subject but MUST NOT contain a <body/> element (or a <thread/> element). In accordance with the core definition of XMPP, other child elements are allowed (although the entity that receives them might ignore them).
Reproduce by sending:
to a room (where you are allowed to change the subject), you receive
<message type='groupchat' firstname.lastname@example.org/a'><subject>ho</subject></message>
indicating that the subject was changed. Can be confirmed by inspecting the internal data structure.
Please provide a link to the specification:
Tested with versions:
- 0.10 4b4cf0167391
- trunk f4d51870d212
The current behavior may be justified if there are clients that would interpret messages with both subject and body as a legitimate subject change.
Another option would be to reject such messages.
Moving this to the next milestone. Let's make the change and see what breaks.