Bug 20732 - doesn't send a part message when leaving Clique rooms
Summary: doesn't send a part message when leaving Clique rooms
Status: RESOLVED MOVED
Alias: None
Product: Telepathy
Classification: Unclassified
Component: salut (show other bugs)
Version: unspecified
Hardware: Other All
: lowest enhancement
Assignee: Telepathy bugs list
QA Contact: Telepathy bugs list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-18 10:46 UTC by Simon McVittie
Modified: 2019-12-03 19:39 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Simon McVittie 2009-03-18 10:46:46 UTC
+++ This bug was initially created as a clone of Bug #20728 +++

Rob wrote, in Bug #16886:
> The spec (and MUC implementation in Gabble) implies that you can leave a MUC
> room with a message by using RemoveMembers([self_handle], "you guys suck")
> [...] this in fact doesn't work. tp-glib doesn't allow removing even the self
> handle from the MUC, because the _CAN_REMOVE flag isn't set.

telepathy-spec 0.17.21 mandates this behaviour (and also the same for StreamedMedia calls), and telepathy-glib 0.7.27 provides the necessary support code in TpGroupMixin. Salut should be updated to make use of this in its Text/ROOM channels.
Comment 1 Simon McVittie 2010-05-20 03:38:01 UTC
Fixed in git for 0.3.12
Comment 2 Simon McVittie 2010-05-20 04:10:20 UTC
0.3.12 fixes the spec compliance issue, but I'm reopening this for an enhancement to the Clique protocol: ability to send a message when leaving a room.
Comment 3 GitLab Migration User 2019-12-03 19:39:23 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-salut/issues/15.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.