Closed Bug 71932 Opened 24 years ago Closed 11 years ago

[RFE] Reload support for attachments

Categories

(MailNews Core :: Composition, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 722929
Future

People

(Reporter: burnus, Unassigned)

References

(Blocks 2 open bugs)

Details

When attaching a file or a webpage this file is immeadiately loaded (I'm not sure whether this is true for the files or if they are read after one hits "Send( later)"). It would be nice if there is a menu item (e.g. a context menu (item)) in which one could choose reload file to make sure an updated version of this file/webpage gets sent. (Especially for the case "Edit as new")
markign NEW.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Reload support for attachments → [RFE] Reload support for attachments
Status: NEW → ASSIGNED
Target Milestone: --- → Future
QA Contact: esther → trix
Product: MailNews → Core
Assignee: ducarroz → nobody
Status: ASSIGNED → NEW
QA Contact: stephend → composition
Product: Core → MailNews Core
(In reply to Tobias Burnus from comment #0) > When attaching a file or a webpage this file is immeadiately loaded (I'm not > sure whether this is true for the files or if they are read after one hits > "Send( later)"). It would be nice if there is a menu item (e.g. a context > menu > (item)) in which one could choose reload file to make sure an updated > version > of this file/webpage gets sent. > (Especially for the case "Edit as new") Current behaviour wrt "attach immediate snapshot" vs. "attach updated version when sending" is not nearly as simple as that, it depends on many factors and is pretty much unpredictable for the end user. So this is part of the bigger scheme of things and proposals listed in attach-paragim-fail tracker bug 877159. This looks like a duplicate of bug 722929, on the assumption that the "attach web file" case is not fundamentally different from the "attach any file" case. Forward-duping because bug 722929 is in a more advanced state with more analysis of current behaviour.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.