On Fri, Jan 6, 2012 at 6:06 PM, Matthew Miller <[email protected]> wrote: > > On Jan 4, 2012, at 03:57, Kevin Smith wrote: > > >> I think we should be avoiding mandating (at least non-security >> critical) UI features - I think this is a simple tweak from normative >> 'SHOULD' to 'is suggested' or similar. >> > > The more I ponder this, the more I think there needs to be some mandating. > What about the following: > > Upon receiving an inbound or outbound <em>gone</em> chat state (as a > carbon copy) for a given conversation, the client SHOULD visually indicate > the conversation is terminated. It is suggested that the conversation be > removed from user display as if the user on the copied client had terminated > the conversation.
I'm happy with the notion of what's suggested, but unless they effect a security or interoperability issue I don't think UI choices should be normative. In this case, failure to observe the suggested SHOULD doesn't seem to really have much bearing on anything other than a slightly surprising user experience. We can suggest how client authors should structure their UIs, but if they feel they should make receiving a <gone/> not indicate the conversation is over, it seems that that's ok. I do not care sufficiently to die on said hill, however. /K
