Open Bug 483575 Opened 15 years ago Updated 1 year ago

Draft loses star mark when saving after an edit

Categories

(Thunderbird :: Message Compose Window, defect)

defect

Tracking

(Not tracked)

People

(Reporter: bugzilla, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2

A draft, already saved and Marked with a star, loses that star if I open the draft, edit it and save it again. This bug was also in Thunderbird 2.

Reproducible: Always

Steps to Reproduce:
1. Save a draft
2. Mark it with a star
3. Open the draft in edit mode, change something in the message
4. Save the draft

Actual Results:  
Now the Star (mark) is gone! :(

Expected Results:  
The Star (mark) should still be there.
confirmed. but I wonder what is your use case?
do you keep a gazillion drafts like i do?

edit as new keeps starred.
edit and don't save keeps starred.
Severity: normal → minor
Summary: Draft loses "Mark" when saving after an edit → Draft loses star "Mark" when saving after an edit
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: x86 → All
Summary: Draft loses star "Mark" when saving after an edit → Draft loses star mark when saving after an edit
It is also loosing TAGS put on a draft message after sending the message.

Use case is following: I want to mark "messages I'm waiting an answer for" with a tag (like "Expect Answer"), when composing the message. The TagToolbar extension would be very handy to do that.
Or whatever other tag to classify the message I'm sending.

On TB3.1RC2
Sorry, ignore my previous comment here, I filed it against the wrong bug :(
(should have been bug 497105).
Severity: minor → S4

I have the list sorted by star and I thought that the star means "important" because the GUI strings say so. Being important does not change when I fix a typo.

To generalize, the IMAP limitation amounts to an implementation detail for the client app, because the user metaphor is to modify an object, rather than to clone an object partway.

I can understand exposing this backend limitation, if you take the star to mean e.g. "review this later", but then the GUI strings should change and the editing form should allow to set the star again before saving, otherwise the message goes down a screen in the list (which is sorted by star in my case) and I have to scroll and find it to set the star.

I asked for this in k-9 also: https://github.com/thundernest/k-9/issues/6652

You need to log in before you can comment on or make changes to this bug.