Tim 'Tool-Man' Taylor wrote:
> That's a power user edge case. It isn't something a normal user is
> concerned about when they want to share a page. Anyhow, before I get
> swatted for trying to make something true by stating it as fact,
> let's consider what the use cases for sending a page snapshot are:
>
> * archiving the page
> * Web page QA
>
> I think those are both pretty narrow use cases. There are probably
> some others.
No. I am one of those who like to archive mail. If I'm pulling an email
out of my archive after a year, the original webpage is likely to be
gone already. So, at that point, it might be nice to have the full page
embedded in the msg itself, so it is stored in my mail archive.
Otherwise, it might be hard to make still sense out of the mail. Of
course, it depends a lot on the mail: No need to save the current page
<http://www.netscape.com>, if all I wanted was a refernce to the company
Netscape. OTOH, if I was joking about a specific part of the page, it
might be gone even as soon as tomorrow (e.g. when the recipient reads it).
> When you write "'saving' the page" do you mean what I suggested above
> about "Save as" in a browser window? I think you do.
No, I meant to be able to save the full page (with images etc.) together
with the mail.
> So where are we at? Should I add two bugs: one for viewing
> multipart/related email
Doesn't that work already?
> and another to enable "Save as"|"Send page" to save|send
> multipart/related files|attachments?
That should be 2 bugs. "Save As" might be filed already, dunno.
