Bug 128321 - Drawing object becomes write-protected when it is moved next to a table of contents
Summary: Drawing object becomes write-protected when it is moved next to a table of co...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: TableofContents-Indexes Shapes
  Show dependency treegraph
 
Reported: 2019-10-22 10:04 UTC by Marc Wuillemin
Modified: 2019-11-10 19:50 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Document to quickly reproduce the issue (12.34 KB, application/vnd.oasis.opendocument.text)
2019-10-22 10:09 UTC, Marc Wuillemin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marc Wuillemin 2019-10-22 10:04:05 UTC
Description:
If a drawing object (e.g. a rectangle) is moved to or created right next to a table of contents, it becomes write-protected. Attempts to delete it result in the message box "Write-protected content cannot be changed. No modifications will be accepted."

Steps to Reproduce:
1. Create a table of contents
2. Create a drawing object (e.g. a rectangle) on the left or right side of the TOC
3. Deselect it
4. Select it and press DELETE

Actual Results:
The drawing object does not get deleted and the message box mentioned above appears.

Expected Results:
The drawing object should get deleted immediately.


Reproducible: Always


User Profile Reset: No



Additional Info:
A possible workaround is to move the drawing object to below the table of contents, deselect it, select it and press DELETE. It gets deleted correctly.

Bug observed in LO 6.2.7.1 and 6.3.2.2 in both Windows and Linux.
OpenOffice 4.1.7 does not show this behavior.
Comment 1 Marc Wuillemin 2019-10-22 10:09:12 UTC
Created attachment 155229 [details]
Document to quickly reproduce the issue
Comment 2 dave.mueller 2019-10-22 12:14:51 UTC
Version: 6.4.0.0.alpha1 (x64)
Build ID: cc57df8f942f239d29cb575ea5a7cb01405db787

Problem is present in this version too.
Comment 3 Dieter 2019-10-27 13:00:48 UTC
(In reply to dave.mueller from comment #2)
> Version: 6.4.0.0.alpha1 (x64)
> Build ID: cc57df8f942f239d29cb575ea5a7cb01405db787
> 
> Problem is present in this version too.

Dave, if you can reproduce a bug, you are allowed to set status to NEW

=> NEW because of comment 2
Comment 4 Cor Nouws 2019-11-10 19:50:50 UTC
already in 3.3.0