(no subject)
Dec. 9th, 2008 12:39 pmDear Apple Design Assholes:
Just because your mail program *can* read an attachment, and *can* put that attachment to be viewed in the body of an email, this does not mean that it SHOULD do so. However, doing so is harmless - as long as you remember that this is an ATTACHMENT and hence it was probably meant to be saveable SEPARATELY FROM THE MESSAGE.
When I have to go back and zip up and resend a .csv file because not only did you display it inline but you actively prevented the end user from saving it back out as the CSV file? You suck.
No love,
Me.
Just because your mail program *can* read an attachment, and *can* put that attachment to be viewed in the body of an email, this does not mean that it SHOULD do so. However, doing so is harmless - as long as you remember that this is an ATTACHMENT and hence it was probably meant to be saveable SEPARATELY FROM THE MESSAGE.
When I have to go back and zip up and resend a .csv file because not only did you display it inline but you actively prevented the end user from saving it back out as the CSV file? You suck.
No love,
Me.