Summary: | EDITING: Showing track changes moves cursor to last deleted comment | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | rubbercheese <rubbercheese> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | normal | CC: | dgp-mail |
Priority: | medium | ||
Version: | 7.0.4.2 release | ||
Hardware: | All | ||
OS: | All | ||
See Also: | https://bugs.documentfoundation.org/show_bug.cgi?id=105485 | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 112916, 115709 |
Description
rubbercheese
2022-10-04 19:02:12 UTC
Thank you for reporting the bug. Please copy and paste informations from Help -> About LibreOffice. Please make sure, that you use the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ => NEEDINFO Here's the info: Version: 7.0.4.2 Build ID: 00(Build:2) CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3 Debian package version: 1:7.0.4-4+deb11u4 Calc: threaded Does it make sense to download a more recent version from libreoffice.org? 7.0.4.2 is the latest version packaged for Debian stable. ~ $ libreoffice --version LibreOffice 7.0.4.2 00(Build:2) ~ $ sudo apt-get upgrade libreoffice Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following NEW packages will be installed: libreoffice 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 206 kB of archives. After this operation, 225 kB of additional disk space will be used. Do you want to continue? [Y/n] Get:1 http://security.debian.org/debian-security bullseye-security/main amd64 libreoffice amd64 1:7.0.4-4+deb11u4 [206 kB] Fetched 206 kB in 0s (594 kB/s) Selecting previously unselected package libreoffice. (Reading database ... 380306 files and directories currently installed.) Preparing to unpack .../libreoffice_1%3a7.0.4-4+deb11u4_amd64.deb ... Unpacking libreoffice (1:7.0.4-4+deb11u4) ... Setting up libreoffice (1:7.0.4-4+deb11u4) ... ~ $ libreoffice --version LibreOffice 7.0.4.2 00(Build:2) I've tried to reproduce with the following steps: 1. Open a new document and write some text. 2. Insert two comments. 3. Save as docx and close LO. 4. Open docx-file. Cursor is within text body. 5. Tool -> Options -> LibreOffice -> User Data 6. Change Fornames/Surnames/Initials (can't find "profile name" as mentioned in comment 0) 7. Track changes record on and show track changes off 8. Delete first comment. Cursor is in text body 9. Show track changes on. Actual result: Cursor disappears Expected result: Cursor still at same place Rubbercheese, are this the correct steps. If not, please make correction. => NEEDINFO Thanks for testing this, Dieter. Yes, the steps are as you've described them. The only adjustment I'd make is in your "actual result". Instead of "cursor disappears", I'd write, "cursor moves into deleted comment", the deleted comment now being visible on account of step 9 (and bug 105485?). Just tested this again following the steps exactly as you've described them and that's the result I get. To be clear, I've been writing text in the comments. Playing around just now, I've been able to get the same result with fewer steps. At present, this (saving as .odt) also produces the undesired result for me: 1. Open a new document and write some text. (Show track changes is on.) 2. Insert two comments (write some text in each). 3. Save as odt and close LO. 4. Open odt-file. Cursor is within text body. 5. Track changes record on and show track changes off 6. Delete first comment. Comment is still visible, but struck out. Cursor is in text body 7. Show track changes on. This will also produce it (no save at all): 1. Open a new document and write some text. (Show track changes is on.) 2. Insert a comment (write some text in it). 3. Track changes record on. 4. Delete first comment. Comment is still visible, but struck out. Cursor is in text body. 5. Show track changes off and then on again. The reason I added in the saving and changes of user data was that I was finding that sometimes when I deleted a comment it would disappear rather than persisting (even with tracked changes set to visible). I'm not sure what's different now, but it appears that saving and changing user data was not needed to have deleted comments persist in struck-out form. It doesn't seem to be anything specific to the LO configuration associated with my user account: 1. Create a new system user account. 2. Switch to it. 3. Open Writer, generate a new document and write some text. (Show track changes is on.) 4. Insert a comment (write some text in it). 5. Switch track changes record on. 6. Delete first comment. Comment is still visible, but struck out. Cursor is in text body. 7. Toggle show track changes off and then on again. Result: Cursor jumps into the comment. Expected: Cursor stays put. Yes, I can see cursor in deleted comment => NEW |