Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
gajim
gajim
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 210
    • Issues 210
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 22
    • Merge Requests 22
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gajim
  • gajimgajim
  • Issues
  • #9491

Closed
Open
Opened Dec 08, 2018 by Zash@Zash

Treatment of groupchat message with both subject and body elements

Please first check if another issue has been opened for your problem

Versions

  • OS: Debian Linux
  • Gajim version: 1.1.91+d129f555
  • GTK version: 3.22.11
  • Python-nbxmpp version: 0.9.90

Steps to reproduce the problem

  1. Receive from a MUC
<message type="groupchat">
  <subject>Did you know</subject>
  <body>Normal groupchat messages can have a subject line</body>
</message>

Expected behavior

The message is treated as a groupchat message and the <body> content is shown. If individual messages can be rendered with a subject, then do that maybe?

Actual behavior

The topic is changed. The <body> content is not shown.

Specification

XEP-0045 says

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).

Note: A message with a <subject/> and a <body/> or a <subject/> and a <thread/> is a legitimate message, but it SHALL NOT be interpreted as a subject change.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gajim/gajim#9491