Created attachment 174688 [details] Zip file of screenshot and repro .odt 1. Make a comment on one word. 2. Make a second comment on a span of other words that ends at the same point. Result: the second comment does not show the starting point of the text span it refers to. So you can't see just what text it applies to. If you extend the second comment so it ends one character later, the second comment will be correctly highlighted in the document body. See attached file.
I can't confirm it with Version: 7.2.1.2 (x64) / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 4; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL Luke, could you please retest with Lo 7.2? Thank you => NEEDINFO
Created attachment 175071 [details] Screenshot and updated sample .odt Retested with: Version: 7.2.1.2 / LibreOffice Community Build ID: 87b77fad49947c1441b67c559c339af8f3517e22 CPU threads: 8; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded I opened the file I had provided, and it looked correct - comments appeared okay. But then I tried to add a couple of comments in the same way, and I saw the bug is still there for the text and comments I'd just added. Screenshot and updated sample .odt provided in a new .zip attachment.
(In reply to Luke Kendall from comment #2) > But then I tried to add a couple of comments in the same way, and I saw the > bug is still there for the text and comments I'd just added. I also added a comment and a second comment in the described way and still couldn't reproduce. Tested with selection from left to right and from right to left. (Perhaps it's only a problem in Linux?) Does it also happen in SafeMode? (Help => Restart in Safe mode)? BTW: You can't confirm your own bugs => status UNCONFIRMED
(If I confirmed the bug, I didn't mean to!) No, restarting in safe mode made no difference. (That took longer than expected because resizing the Writer window in safe mode so I could see your note caused a hard lockup of the Marco desktop and I had to power cycle my system: I couldn't even get to a console. I've had the Zoom app do the same thing.)
(In reply to Luke Kendall from comment #4) > No, restarting in safe mode made no difference. So further ideas from my side. I hope somebody else can help and confirm.
Hello Luke, perhaps bug is only reproducible in Linux, so I can't confirm it. But a new major release of LibreOffice is available since this bug was reported. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Dear Luke Kendall, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear Luke Kendall, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp