6.0.0-beta1
8/10/25

[#1979] auto_save_draft expansion of recompose functionality
Summary auto_save_draft expansion of recompose functionality
Queue IMP
Queue Version HEAD
Type Enhancement
State Resolved
Priority 1. Low
Owners
Requester liamr (at) umich (dot) edu
Created 05/16/2005 (7391 days ago)
Due
Updated 11/24/2006 (6834 days ago)
Assigned
Resolved 11/24/2006 (6834 days ago)
Milestone
Patch No

History
11/24/2006 05:57:28 AM Chuck Hagenbuch Comment #3
State ⇒ Resolved
Reply to this comment
Going to resolve this since it's the kind of thing that DIMP does, and 
that will require javascript anyway going forward, so the dimp-style 
interface will always cover it.
08/11/2006 02:53:30 PM Chuck Hagenbuch Comment #2 Reply to this comment
See the code we have for this in DIMP.
10/23/2005 01:28:57 PM Jan Schneider Version ⇒ HEAD
 
05/16/2005 06:04:50 PM Chuck Hagenbuch State ⇒ Accepted
 
05/16/2005 06:03:53 PM liamr (at) umich (dot) edu Comment #1
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ auto_save_draft expansion of recompose functionality
Queue ⇒ IMP
State ⇒ New
Reply to this comment
It would be pretty cool if IMP 4.x's recompose functionality could be 
expanded to provide an "auto save draft" function.. so if a user's 
browser crashed or was closed while composing a message, the user 
could recover the message they were working on.



Not sure where it would store it..  I'd hate to fill the draft folder 
w/ multiple copies of the same message over and over again.   Perhaps 
saving over the same message in drafts and deleting the message from 
the drafts folder when the message was sent?

Saved Queries