Created attachment 111043 [details] example odt with tracked changes for comment function behavior for the first change Problem statement for Win7/64 LibO 4.4.0.0. Beta2 (RC2)!: If you open a document with tracked changes and the icon bar for changes is displayed and you click on the right arrow to find the first change (cursor is after opening at the beginning of the document) the first change is marked. In the icon bar the icons for accepting or refusing this change is enabled, not the icon for the comment. When you click on the right arrow icon again (the next change is marked) and on the left arrow to move to the first change again, now the comment icon is enabled and you can use it. The same disable/enable behaviour is seen in the menu Edit-Changes not only in the icon bar. Expectet behaviour: Even with the first move to the first change I want to give a comment on it, so even with the first step to the first change the comment icon / menu entry is enabled. Steps to reproduce the behaviour: 1. Open Writer and enable the change tracking icon bar. 2. Open the document I will provide here, it is with a few tracked changes 3. After opening the Cursor is located at the first position in the first page 4. click icon next change, the next changed line is selected 5. in the icon bar the accept and refuse icons are enabled, the comment icon not. 6. click next change, click last change 7. the comment icon is enabled.
Reproducible with LO 4.4.0.0.beta1 (Win 8.1).
Hi Lothar, * I think this works fine in 5.0.2.2 Comment on change is not always active, but comment is. OK?
.
Hi Cor, thanks for caring about this bug. But sorry, this is not the same for me, a comment to the text is not the same as the comment to a tracked change, as it is handled in the commit/discharge dialog with accepting changes. If it should be the same, two icons makes no sense and the fact, that after hitting next and hitting back it works, seems to me that these are two different kind of comments. So, for me it doesn't work also with 5.0.2.2 I don't know if I'm alloud to reopen the bug, but if, i would reopen it ;-) Cu, Lothar
(In reply to riesslibo from comment #4) > So, for me it doesn't work also with 5.0.2.2 > I don't know if I'm alloud to reopen the bug, but if, i would reopen it ;-) Sure you are. But let me reopen it for you: indeed it is not OK. Any idea if it worked fine in a previous version? (Hmm I think the Track Changes tool bar wasn't available that long ago.)
confirmed
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170103
Another example attachment 106821 [details] from Bug 84300. Confirmed with libo-master~2017-04-16_23.49.21_LibreOfficeDev_5.4.0.0.alpha0_Win_x86. Looks like bug from the implementation in 4.0.
** Please read this message in its entirety before responding ** 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
*** This bug has been marked as a duplicate of bug 79197 ***