GNOME Bugzilla – Bug 713908
Display latest message in completely read conversation for preview
Last modified: 2019-01-15 06:40:29 UTC
---- Reported by jim@yorba.org 2013-10-02 19:06:00 -0700 ---- Original Redmine bug id: 7585 Original URL: http://redmine.yorba.org/issues/7585 Searchable id: yorba-bug-7585 Original author: Jim Nelson Original description: This is a corner-case, but when seen leads to unintuitive results. The current logic in the conversation list is to display the oldest unread message as the preview. This is by design (#5921). However, if all messages are read in a conversation, the logic is to use the newest in-folder message for the preview, falling back on the newest out-of-folder message. (Since the conversation can only be displayed if one or more messages is in-folder, the latter should never be necessary.) It is possible, however, for the newest message to be out-of-folder. Eric saw this situation in his Important folder where earlier messages were heuristically marked by Gmail as Important but the newest message was not. If the newest message is unread, then it becomes the preview message. When the conversation is completely read, the message prior to it (the newest _in- folder_ message) becomes the preview. This is unintuitive. The right course of action seems to be to always use the newest message in a conversation, regardless of its location, as the preview message. Related issues: related to geary - 5921: Conversation list: display oldest unread message as previ... (Fixed) --- Bug imported by chaz@yorba.org 2013-11-21 20:24 UTC --- This bug was previously known as _bug_ 7585 at http://redmine.yorba.org/show_bug.cgi?id=7585 Unknown milestone "unknown in product geary. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution
Resolving as obsolete all bugs that should be resolved by the conversation list redesign (https://bugzilla.gnome.org/show_bug.cgi?id=730682). I'd mark them as a duplicate, but bz won't let me :( Apologies for the noise.