Chrome OS Version: ToT

Steps To Reproduce:
(1) Save an image on an SD card.
(2) Lock the SD card (use write-protect notch).
(3) Insert the SD card.
(4) Open the image from Files app.
(5) Click "Edit" button in the Gallery app.
(6) Rotate the image.
(6) Wait 1 second.

Actual Result:
The app says "Saved".
The edited images are saved to Downloads folder.
"my_image_file - Edited.png"

Expected Result:
- Open the image in non-editable mode, or
- show alert message to tell the file was saved to a different location because the original file was not writable.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always

What is the impact to the user, and is there a workaround? If so, what is
it?
It can be confusing that the edit and save seemingly finishes successfully but the original file is not updated.
This also affects users under the "ExternalStorageReadOnly" policy enabled.

 

Chrome OS Version: ToT

Steps To Reproduce:
(1) Save an image on an SD card.
(2) Lock the SD card (use write-protect notch).
(3) Insert the SD card.
(4) Open the image from Files app.
(5) Click "Edit" button in the Gallery app.
(6) Rotate the image.
(6) Wait 1 second.

Actual Result:
The app says "Saved".
Usually the image is saved back to the original path (i.e. overwrite), but
it is saved to Downloads folder with name like "my_image_file - Edited.png".
The original file remains unchanged.

Expected Result:
Either of these.
- Open the image in non-editable mode, or
- show alert message to tell the file was saved to a different location because the original file was not writable.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always

What is the impact to the user, and is there a workaround? If so, what is
it?
It can be confusing that the edit and save seemingly finishes successfully but the original file is not updated.
This also affects users under the "ExternalStorageReadOnly" policy enabled.