GNOME Bugzilla – Bug 712950
Indicate conversation has attachments in conversation list
Last modified: 2021-07-05 13:26:37 UTC
---- Reported by jim@yorba.org 2012-06-08 12:36:00 -0700 ---- Original Redmine bug id: 5369 Original URL: http://redmine.yorba.org/issues/5369 Searchable id: yorba-bug-5369 Original author: Jim Nelson Original description: The conversation viewer will soon have a nice paperclip icon for messages that have attachments (#3809). It would be nice if the conversation list displayed a similar icon when any of the messages in a conversation has attachments. (Gmail does this.) To make good use of space, I propose we add two icons to the application: an envelope with a paperclip attached, and an envelope with a paperclip an a star (indicating unread conversation with attachments). These icons could be used where the unread conversation icon sits today. Related issues: related to geary - 5727: Update conversation list interface (Fixed) blocked by geary - Feature #3809: view/extract attachments (Fixed) ---- Additional Comments From geary-maint@gnome.bugs 2012-09-25 15:03:00 -0700 ---- ### History #### #1 Updated by Adam Dingle over 1 year ago * **Priority** changed from _Normal_ to _High_ * **Target version** set to _0.2_ #### #2 Updated by Jim Nelson about 1 year ago * **Assignee** set to _Daniel Fore_ I've asked Daniel to come up with two icons: one an envelope with a paperclip (unread conversation w/ attachments) and the other simply a paperclip (read conversation w/ attachments). This plus the existing unread-conversation icon and using blank space to indicate a read conversation w/ no attachments gives us all the assets we need to implement this in accordance with the final decision of #5727. #### #3 Updated by Daniel Fore about 1 year ago Hey Jim, I think we're going to have an issue with this plan. The problem would be that we could add an icon to signify both unread and attachments but the default theme already comes with the icons for unread or attachment. So when we have a mail that is only either unread (with no attachments) or has an attachment (but is read) we may end up with an icon that looks completely different than the system unread and attachment icons. So we could either not use the system icons for unread and attachments (which, imo, is less preferable). Or we could display the icons separately (which might take a little more space to do). #### #4 Updated by Daniel Fore about 1 year ago * **File** attachment.svg added * **Assignee** changed from _Daniel Fore_ to _Jim Nelson_ Okay, so we after some discussion, we've decided to try placing a symbolic paperclip icon in-line with the sender list a la iOS Mail. In order to do this, we needed a small (but wide) icon that wouldn't alter the convo list height. Attached here is this icon. #### #5 Updated by Jim Nelson about 1 year ago * **Assignee** deleted (<strike>_Jim Nelson_</strike>) * **Target version** deleted (<strike>_0.2_</strike>) This is more difficult than first appears. Geary is unable to tell when a message has an email has an attachment until the entire body has been downloaded, but there's currently no clean way for the Conversation List to be notified when this occurs. With time short for this release, this will need to be deferred to 0.3. --- Bug imported by chaz@yorba.org 2013-11-21 20:18 UTC --- This bug was previously known as _bug_ 5369 at http://redmine.yorba.org/show_bug.cgi?id=5369 Imported an attachment (id=260533) Unknown version " in product geary. Setting version to "!unspecified". 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
CC'ing fede@inventati.org since he mentioned in Bug 765516 this was an issue.
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new ticket at https://gitlab.gnome.org/GNOME/geary/-/issues/ Thank you for your understanding and your help.