Bug 160950 - Warn before performing a destructive/lossy edit of OLE object
Summary: Warn before performing a destructive/lossy edit of OLE object
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
24.8.0.0 alpha0+
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: OLE-Objects
  Show dependency treegraph
 
Reported: 2024-05-06 08:41 UTC by Eyal Rozenberg
Modified: 2024-05-06 13:50 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eyal Rozenberg 2024-05-06 08:41:54 UTC
Some OLE objects are editable in LO in a way with is rather destructive. Example: PDF documents. When one:

1. Adds a PDF document as an OLE object.
2. Right-clicks, and chooses Edit on the context menu

It would be useful it LO would warn the user that editing the PDF may result in degradation of the document regardless of concrete changes the user makes.

No additional warnings need be give on repeated edits

Bikeshedding I: How do we decide which formats are "safe" to edit with no warnings?

Bikeshedding II: Should the warning be given once per object? Once per (LO session, object)? And there are other options even.


Note: If such a warning is made, then the significance of bug 160949 decreases somewhat.
Comment 1 Heiko Tietze 2024-05-06 13:40:38 UTC
Properties > Options > Protect > Contents - does not disable/hide the Edit function and allows to change the content => bug.

Other than that I could imagine a solution per frame/section that is made read-only.
Comment 2 Eyal Rozenberg 2024-05-06 13:50:32 UTC
(In reply to Heiko Tietze from comment #1)
> Properties > Options > Protect > Contents - does not disable/hide the Edit
> function and allows to change the content => bug.

Filed as bug 160962; but that's a different issue.

> Other than that I could imagine a solution per frame/section that is made
> read-only.

No, I mean for content that is _not_ read-only nor protected. Novice users will not realize that the mere act of opening some OLE objects for editing - changes them significantly, possibly degrading them.