https://bz.apache.org/ooo/show_bug.cgi?id=126877
--- Comment #1 from Jason Spencer <[email protected]> --- Just noticed Issue 73155 makes the same case, and points out implications in user experience. Also, several of the arguments against this request usually state that the email client or web browser saves the file as read-only--what can OO do? The answer is "make it writable." Another response is, "Then if you change it and close it, the client may delete it afterwords and your changes are lost!" My response is, "yeah, good." There are many workflows using the great OO suite. Things can be saved to pdf's, emailed straight from the app, manipulated for viewing purposes and thrown away, etc. Making changes to save securely forever is one, but as other actions are supported, it becomes a less-frequent option. Hope that helps show the community desire for this enhancement. -- You are receiving this mail because: You are the assignee for the issue.
