Description: Anchor position on file open different from file save Steps to Reproduce: 1. Open attachment 160389 [details] 2. Click a picture & look at the anchor 3. Click somewhere in the text 4. Press CTRL+A 5. CTRL+C 6. CTRL+N 7. CTRL+V 8. Look at the anchor.. should be at the end of the line oooa Actual Results: Position of anchor on file open wrong Expected Results: Should be at the end of the line like after paste Reproducible: Always User Profile Reset: No Additional Info: Found in Version: 7.0.0.0.alpha0+ (x64) Build ID: 97a2c1fc5e376c0c00968f17a0392c6d3a5ed565 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: and in 4.4.7.2
Created attachment 160391 [details] Screenshot
Well, for me, the anchor is not at the end of the line oooa to begin with. It also doesn't change with step 7. Win & Linux master. Maybe re-test
Created attachment 164941 [details] Screencast
Version: 7.1.0.0.alpha0+ (x64) Build ID: 1e0cfd5662d95cea84e80e4fe10d52c3b1101ae6 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: nl-NL (nl_NL); UI: en-US Calc: CL
Ok, at step 8 you meant the position of the anchor *in the pasted document* will be at the end of the line oooa. I thought this "should" referred to some expected initial state of the original document. My initial anchor position is not as far away from the end as in your screenshot & screencast. In 3.5.0 and 3.3.0 we can't Ctrl-A + copy the images. Arch Linux 64-bit Version: 7.1.0.0.alpha0+ Build ID: d784e711c102f204552c3c816636da01b1085f61 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 29 August 2020
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