Description: Calc: Navigator shows new added comment only after changing width of any column Steps to Reproduce: 1. Open new Calc document 2. Open Navigator (F5) 3. Add any comment to any cell (Insert-Comment) 4. Look to Navigator => there isn't your added comment in section "Comments" 5. Change width of any column (drag column heading separator to right for example) 6. Now Navigator shows your added comment If you try add new sheet, then Navigator will show it at once without any additional action from you Actual Results: Navigator shows new added comment only after changing width of any column Expected Results: Navigator shows new added comment after adding at once Reproducible: Always User Profile Reset: No Additional Info: Версия: 6.5.0.0.alpha0+ (x64) ID сборки: 42a1a1c6b91907f81e15066ffab219411f18c4db Потоков ЦП: 4; ОС:Windows 10.0 Build 18362; Отрисовка ИП: по умолчанию; VCL: win; Локаль: ru-RU (ru_RU); Язык интерфейса: ru-RU Calc: threaded
hm...note for QA: try insert several comments in several cells for repro. I see strange behaviour now, when Navigator shows first comment at once, but don't show all next comments
(In reply to Roman Kuznetsov from comment #1) > hm...note for QA: try insert several comments in several cells for repro. I > see strange behaviour now, when Navigator shows first comment at once, but > don't show all next comments repro also in Версия: 4.4.7.2 ID сборки: f3153a8b245191196a4b6b9abd1d0da16eead600 Локаль: ru_RU
Confirmed with Version: 6.5.0.0.alpha0+ (x64) Build ID: 8f25472d3de4f43cf594fa41ebfba2a1b01d4c9d CPU threads: 12; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win; Locale: ru-RU (ru_RU); UI-Language: en-US Calc: CL Not only resizing columns refreshes comments list in navigator, but also other changes, like entering something into any cell.
Dear Roman Kuznetsov, 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
Still a problem in Version: 7.2.4.1 / LibreOffice Community Build ID: 27d75539669ac387bb498e35313b970b7fe9c4f9 CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
abandoned patch code pointer https://gerrit.libreoffice.org/c/core/+/159731
(In reply to Justin L from comment #7) > abandoned patch code pointer https://gerrit.libreoffice.org/c/core/+/159731 Same patch was used to fix bug 158652. *** This bug has been marked as a duplicate of bug 158652 ***