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 |
State ⇒ Resolved
that will require javascript anyway going forward, so the dimp-style
interface will always cover it.
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ auto_save_draft expansion of recompose functionality
Queue ⇒ IMP
State ⇒ New
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?