When a user navigates a number of folders and files, the user may encounter files to which the user has read-only access.
This should not prevent the user from editing the contents, but does prevent the user from saving back the document to the original location.
The solution is to "force" the user to first create a read-write copy (that is not otherwise shared implicitly), clarifying the process to the user by forcing them to select a location to save the copy.
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T67 Real-time Collaborative Document Editing | ||
| Restricted Maniphest Task | ||||
| Resolved | machniak | T757 Editing a read-only document |
But isn't preventing them from saving back fine?
If they edit the contents, they've "staged" changes, so to speak, and only the person with write privileges can actually save it back.
For me this should look like:
Or in 2. we could have inactive "Save" button and new button "Save As" displayed with the same logic.