Created attachment 130732 [details] Spreadsheet with steps 1-4 1. Start a new Calc spreadsheet. 2. Resize a row, let's say row 9. 3. Insert a comment for a cell below that row, let's say D10. 4. Right click cell, select Show Comment. Attaching a spreasheet with the steps so far. 5. Resize the same row as before (row 9) to around its original size. 6. Move the comment a large distance, quickly. Or move it to the right, and with another move, move it back to left. => The comment's arrow now points to top left corner of the sheet. Or maybe just somewhere else in the sheet, like around its original place, but not the cell it's supposed to. What happens is not entirely consistent for me... If it can't be confirmed easily, I'll try to create a screencast. Observed with 5.3.0.3, 4.0.0.3, 3.3.0 / Ubuntu 16.04.
Unable to repro from scratch of with file. Have to test on Linux l8r. Win 7 Pro 64-bit Version: 5.4.0.0.alpha0+ Build ID: c6dd735afb2e1b3837c4f8c5659f52fafab4c56f CPU Threads: 4; OS Version: Windows 6.1; UI Render: default; TinderBox: Win-x86@42, Branch:master, Time: 2017-01-30_01:52:54 Locale: fi-FI (fi_FI); Calc: group
Created attachment 130894 [details] Screenshot after moving comment I think I moved it twice here using 5.3.0.3 / Windows 7. There are no accurate steps, I kind of did it trial by error. Should I create a screencast to illustrate?
(In reply to Aron Budea from comment #2) > There are no accurate steps, I kind of did it trial by error. Should I > create a screencast to illustrate? You totally should.
Created attachment 130911 [details] Screencast I totally have, then. Seems like the arrow ends up pointing to the place where it originally was before resizing the cell. Or sometimes it points to the top left corner instead.
Tried on Ubuntu 16.10, but could not repro. I tried to follow the screencast closely, including having the row have a height where the comment height is smaller (so it goes "inside" the row). Version: 5.4.0.0.alpha0+ Build ID: a296a69c984b17cfbcd249cf6bdc191d08dff2a6 CPU Threads: 4; OS Version: Linux 4.8; UI Render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF-dbg, Branch:master, Time: 2017-02-06_01:05:34 Locale: en-US (en_US.UTF-8); Calc: group
Created attachment 131158 [details] Bug about to occur I only managed to get this on the 4-5th try myself. Also, if it doesn't occur, just undo until after the row resizing after adding the comment, and try again. A telltale sign of the bug if the arrow stops pointing to the cell during dragging. Sometimes it happens easier after undoing and giving it another go.
repro. Version: 6.0.0.0.alpha0+ Build ID: 77f77c57d336ba041faf51e2168372d1e0962a19 CPU threads: 4; OS: Linux 4.4; UI render: default; VCL: gtk2; TinderBox: Linux-rpm_deb-x86_64@70-TDF, Branch:master, Time: 2017-06-29_23:40:47
*** Bug 111449 has been marked as a duplicate of this bug. ***
Steps to Reproduce: 1. Open Calc 2. Select B6 and press CTRL+ALT+C (add comment) and enter XXX 3. Menu -> View -> Show comment (not needed; more for a visual) 4. Insert a new sheet -> Sheet insert -> Click OK 5. Select F16 and press CTRL+ALT+C (add comment) and enter ZZZ 6. Select C16 7. Menu -> View -> Show comment 8. Press CTRL+Z three times (3x) 9. Comment will appear at C11 on sheet 1
*** Bug 116580 has been marked as a duplicate of this bug. ***
Another way Insert comment on cell A1, B1, C1 Merge the cells Show comment Comment is displayed on cell A1 even though they are merged now (should be outside of the merged region) https://screencast-o-matic.com/watch/cFfrjebifH
Version: 6.1.0.0.alpha0+ (x64) Build ID: d39a8e791618a40328c0f90bece3cc246dcf57f7 CPU threads: 4; OS: Windows 10.0; UI render: default; TinderBox: Win-x86_64@42, Branch:master, Time: 2018-04-06_00:59:07 Locale: en-US (en_US); Calc: group
(In reply to Telesto from comment #9) Another way to reproduce: 1. Open Calc 2. Insert a comment 3. Show comment 4. Sheet -> Move or copy sheet -> Press OK (copy) 5. Undo (CTRL+Z)
Dear Aron Budea, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Aron Budea, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Still repro with steps from comment 13. Not sure about my original steps, but don't want to dig into that while it's reproducible with some steps. LO 7.3.0.0.alpha0+ (4450137924eb8626a57283e1ab4f4ad62dd2d595) / Windows.
Dear Aron Budea, 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