Bug 132277 - Shapes not properly placed after undoing change of anchor from "To character" to "As character"
Summary: Shapes not properly placed after undoing change of anchor from "To character"...
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:
: 136384 (view as bug list)
Depends on:
Blocks: Anchor-and-Text-Wrap Undo-Redo
  Show dependency treegraph
 
Reported: 2020-04-20 14:51 UTC by Telesto
Modified: 2024-10-29 02:40 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Example file (10.77 KB, application/vnd.oasis.opendocument.text)
2020-04-20 14:52 UTC, Telesto
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Telesto 2020-04-20 14:51:49 UTC
Description:
Shapes not properly places after undoing change of anchor to as character to to character 

Steps to Reproduce:
1. Open the attached file
2. Change the anchoring to 'as character' for both and undo CTRL+Z

Actual Results:
Shapes on a different spot

Expected Results:
Shapes at the same place as initially


Reproducible: Always


User Profile Reset: No



Additional Info:
Version: 7.0.0.0.alpha0+ (x64)
Build ID: 4475bcd83aac7e033fc5250f268eb922bd471e7b
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; 
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CL
Comment 1 Telesto 2020-04-20 14:52:02 UTC
Created attachment 159764 [details]
Example file
Comment 2 Buovjaga 2020-08-25 18:28:22 UTC
Also repro with 4.4.7 and 3.3.0

Arch Linux 64-bit
Version: 7.1.0.0.alpha0+
Build ID: e2fe4fde592564d35099ad1e2659ad682dfb77f5
CPU threads: 8; OS: Linux 5.8; UI render: default; VCL: kf5
Locale: fi-FI (fi_FI.UTF-8); UI: en-US
Calc: threaded
Built on 25 August 2020
Comment 3 Dieter 2020-10-26 07:53:34 UTC
*** Bug 136384 has been marked as a duplicate of this bug. ***
Comment 4 Telesto 2020-10-26 17:34:17 UTC
@Michael,
This does has a lot in common with bug 132533 (at least based on behaviour), so I assume/speculate you might be interested.
Comment 5 QA Administrators 2023-05-13 03:18:56 UTC
Dear Telesto,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug