|Summary:||[1.0?] Consider making Channels never close themselves|
|Product:||Telepathy||Reporter:||Will Thompson <will>|
|Component:||tp-spec||Assignee:||Telepathy bugs list <telepathy-bugs>|
|Status:||RESOLVED MOVED||QA Contact:||Telepathy bugs list <telepathy-bugs>|
|i915 platform:||i915 features:|
Description Will Thompson 2009-07-23 10:40:57 UTC
I don't think that channels should ever auto-close. * wjt doesn't think the CM should close text channels without the UI telling it to smcv: wjt: apropos of? wjt: (apropos of musings about edge cases like: you try to join a room, you're kicked before the channel finishes being dispatched. currently, the handler can't figure out what happened, partly because Group doesn't have "why was i kicked?" properties, and partly because the CM closes the channel when you're kicked.) smcv: wjt: RESOLVED LATER tbh wjt: the spec doesn't say it needs to auto-close :) smcv: in practice, everything does, => UIs probably assume it smcv: so it would be a semantic change to the spec even if the current semantics are largely unwritten smcv: I would not be opposed to "any channel from which you can be kicked MUST be a group", which is a prerequisite smcv: (because to not auto-close, it would have to have an "I'm not here" state, which is "SelfHandle not in Members") * wjt copies into bugzilla and goes back to work :)
Comment 1 Simon McVittie 2014-01-23 19:07:19 UTC
We should maybe think about doing this before 1.0, because it'll be a pain to change otherwise.
Comment 2 GitLab Migration User 2019-12-03 20:18:16 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-spec/issues/28.