Closed Bug 1749115 Opened 2 years ago Closed 1 year ago

opened attachments (using "Open with") are no longer set read only

Categories

(Thunderbird :: Untriaged, defect)

Thunderbird 91
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mikekaganski, Unassigned)

References

Details

Using TB 91.4.1 (64-bit) on Windows 10, opening an attachment using "Open with" does not set read-only attribute on the opened file; that makes the file open in applications in read-write mode, allowing editor application to save to the temporary file without warning, which would then be removed. Inexperienced users may be unaware that they are editing a temporary copy, and might loose their work. Note that 'browser.helperApps.deleteTempFileOnExit' setting is checked to be true. To be specific, I have checked the file properties of the temporary attachment file using Windows Explorer, while the file was opened in editor.

This used to work as expected in earlier versions; see e.g. bug 1095893, closed fixed for TB 37. So this seems to be a regression, which was filed to LibreOffice - see https://bugs.documentfoundation.org/show_bug.cgi?id=146642.

I see that a related line in DownloadIntegration.jsm (setting 'options.winAttributes'), introduced in https://hg.mozilla.org/releases/mozilla-release/rev/b7d8d79c1ee5, was removed ~recently in https://hg.mozilla.org/releases/mozilla-release/rev/aadba76932ea3f20967a69813277a637e3bfa025; however, I have confirmed that at least Firefox 95.0.2 sets the RO bit correctly when "opening with" downloaded files. I do not know if that change is really related to this problem.

It is reported that the same is true for Linux - see https://bugs.documentfoundation.org/show_bug.cgi?id=147277.

OS: Windows → All

Maybe it was fixed because now they open as read only on Arch Linux for me with TB 102.5.1 (64-bit)

Works for me with 102.5.1 (64-bit) on Windows 10.
Thank you!

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.