After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 200948 - should warn user when closing editted composer
should warn user when closing editted composer
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
unspecified
Other All
: Normal major
: ---
Assigned To: Radek Doulik
Evolution QA team
evolution[composer]
: 205006 208472 215652 216006 (view as bug list)
Depends on: 200966
Blocks: 220672
 
 
Reported: 2000-12-06 12:49 UTC by Dan Winship
Modified: 2013-09-10 14:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Dan Winship 2000-12-06 12:49:04 UTC 
The save/cancel dialog should only appear if there's actually text in
the composer.

Ideally, if there's only text in the composer *that wasn't there to
start with*. (ie, sig and reply quoting doesn't count).

Oh, when I say "text" I mean "text or attachments".
Comment 1 Dan Winship 2001-01-08 17:50:31 UTC 
Jeff has made this so it won't prompt you if you haven't changed the headers,
which is good for compose and forward, but bad for reply. So we still need
to be able to tell if the content has changed.
Comment 2 Jason Leach 2001-01-16 15:30:49 UTC 
I'm all over this bug.
Comment 3 Jason Leach 2001-01-25 19:37:27 UTC 
Just committed fixes for all the remaining problems (don't ask about unchanged
forward/replies, ask about attachments too) with this bug except for #966:
composer doesn't know when the message body has changed.
Comment 4 Not Zed 2001-02-01 05:20:01 UTC 
Well now it just closes with no dialogue, even if i've half written a message or
reply.

Is this the intended behaviour? (i dont mind it, if i hit close i expect it to
"f**k off", but i'm not sure others would agree).
Comment 5 Luis Villa 2001-06-26 18:18:35 UTC 
I apologize for the spam; re-setting all target milestones to 'future'
in preparation for evolution 1.0. If you have any questions, please feel
free to write louie@ximian.com.
Comment 6 Dan Winship 2001-07-23 13:41:03 UTC 
*** bug 205006 has been marked as a duplicate of this bug. ***
Comment 7 Dan Winship 2001-09-05 17:49:59 UTC 
*** bug 208472 has been marked as a duplicate of this bug. ***
Comment 8 Nat Friedman 2001-10-10 19:32:31 UTC 
Resetting this for 1.1
Comment 9 Dan Winship 2001-11-19 16:28:45 UTC 
*** bug 215652 has been marked as a duplicate of this bug. ***
Comment 10 Luis Villa 2001-11-26 17:04:01 UTC 
Because of the decision to remap 1.1->1.2 and 1.2->1.4, I'm going to be
moving a large number of bugs around in the bugzilla. You can just
search on 'body contains' 'Because of the decision to remap' and mark
all as read. Please direct all questions about this change to
evolution@ximian.com, not the bug.
Luis
Comment 11 Jeffrey Stedfast 2001-12-06 01:07:24 UTC 
the timeframe for this more or less depends on whether the gtkhtml
editor component has the interfaces to allow this.
Comment 12 Luis Villa 2001-12-12 16:18:13 UTC 
cc'ing gtkhtml maintainers then to get their opinion.
Comment 13 Jeffrey Stedfast 2002-01-04 21:44:22 UTC 
*poke* *poke* gtkhtml devs, what do you guys think of this bug?
Comment 14 Jeffrey Stedfast 2002-01-22 20:30:11 UTC 
*** bug 216006 has been marked as a duplicate of this bug. ***
Comment 15 Radek Doulik 2002-02-12 15:42:14 UTC 
this is implemented in evo/HEAD and gtkhtml/HEAD
Comment 16 Jeffrey Stedfast 2002-04-10 23:13:21 UTC 
*** bug 220672 has been marked as a duplicate of this bug. ***