Created attachment 182237 [details]
Example file

Moves instantly to the left when pressing backspace
Version: 6.3.0.0.alpha0+
Build ID: e3ce6ea30e2cdd81857597f50ef5e0a6acd198ee
CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
Locale: nl-NL (nl_NL); UI-Language: en-US
Calc: CL

centered even after backspace or save
Version: 6.1.0.0.alpha0+
Build ID: e1b247a843c5eb850fe0079819239d9883412d38
CPU threads: 4; OS: Windows 6.3; UI render: default; 
Locale: nl-NL (nl_NL); Calc: CL

Created attachment 182364 [details]
Example file

we place the screen shot for before and after checking the description.

REPRODUCE:

Description:
Position of shape changes at the time of saving (track changes involved)

Steps to done:
1. Open the attached 
2. Place cursor at the start of the heading starting with "Dragging"
3. SHIFT+CTRL+ARROW UP (1x) -> Image frame selected
4. Press backspace
5. Press Save
6. After i doing the above steps some time the image stay at center but some time 
   it suddenly move to left so this is need to check.

(In reply to Telesto from comment #2)
> Moves instantly to the left when pressing backspace
> Version: 6.3.0.0.alpha0+
> Build ID: e3ce6ea30e2cdd81857597f50ef5e0a6acd198ee
> CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; 
> Locale: nl-NL (nl_NL); UI-Language: en-US
> Calc: CL

Bibisected with linux-64-6.4. Changed away from this behaviour in https://git.libreoffice.org/core/commit/1aac73a1fb260e4c76a483a68f003913fdd2c4bb
tdf#125990 change tracking: remove text join workaround

> centered even after backspace or save
> Version: 6.1.0.0.alpha0+
> Build ID: e1b247a843c5eb850fe0079819239d9883412d38
> CPU threads: 4; OS: Windows 6.3; UI render: default; 
> Locale: nl-NL (nl_NL); Calc: CL

Bibisected with linux-64-6.2. Changed away from this behaviour in https://git.libreoffice.org/core/commit/22639148ae5400bac98f32a75d7431b857c80195
tdf#54819 change tracking: keep paragraph style after full deletion

László can comment on this.

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