After removing a custom animation from a slide, the Add... button no longer works. I have to select another slide and then go back to the first one in order to be able to add a new custom animation.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Confirmed in 3.5.0beta1. Changing back to NEW.
not reproducible with LO 4.0.2.2 (Win7 Home, 64bit) Does this issue still persist for you with the latest release of LO? If not, then I would propose to close this bug report.
This bug still exists in 4.0.2.2 (Ubuntu 12.10, 64bit), in a weaker form: Here is what I do step by step: 1. Open an Impress file. 2. Click on a custom animation. 3. Click the Remove button. At this stage, the Add… button is still active. However, no effect is selected. 4. Click the Add… button. 5. Nothing happens, but the Add… button is now greyed out. If I select an effect, the Add… button is reactivated, and I can add another animation. If after deleting an effect its parent were selected, then I would not need this extra click. (This is the same sort of bug as if the text caret disappeared when you press Delete; the difference is that the caret marks a place between characters, whereas here the effective position is on a particular (selected) effect, not between two.) But maybe this is just the way that tree widgets work?
Please attach your presentation file so anyone here could test using same source.
Created attachment 80278 [details] Example file to reproduce bug
> 2. Click on a custom animation. > > 3. Click the Remove button. > > At this stage, the Add… button is still active. However, no effect is > selected. I think it's a bug. > 4. Click the Add… button. > > 5. Nothing happens, but the Add… button is now greyed out. Confirm same behavior on my testing. > If I select an effect, the Add… button is reactivated, and I can add another > animation. If after deleting an effect its parent were selected, then I > would not need this extra click. (This is the same sort of bug as if the > text caret disappeared when you press Delete; the difference is that the > caret marks a place between characters, whereas here the effective position > is on a particular (selected) effect, not between two.) But maybe this is > just the way that tree widgets work? Don't know whether it's a bug or it's designed as is with some consideration. Tested on LO 4.0.4.1 (Win7 32bit)
Version: 4.2.0.0.alpha0+Build ID: b0a1666f756aa5f5315366eca9d7d02ddd55d2b Date: Tue May 28 08:51:01 2013 +0300 Platform: Bodhi Linux 2.2 x64 I can confirm and believe it isn't working as intended - it should gray out immediately. The issue is that after you remove it unselects the object so there is nothing to add an event to. So one of two solutions are needed: 1. Don't unselect the object so you can add immediately 2. Gray out immediately after selecting remove New Minor - doesn't prevent high quality work, can slow it down a tiny bit Low - default seems appropriate ProposedEasyHack - seems relatively easy to solve + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + LibreOffice is powered by a team of volunteers, every bug is confirmed (triaged) by human beings who mostly give their time for free. We invite you to join our triaging by checking out this link: https://wiki.documentfoundation.org/QA/BugTriage and join us on freenode at #libreoffice-qa There are also other ways to get involved including with marketing, UX, documentation, and of course developing - http://www.libreoffice.org/get-help/mailing-lists/. Lastly, good bug reports help tremendously in making the process go smoother, please always provide reproducible steps (even if it seems easy) and attach any and all relevant material
In order to limit the confusion between ProposedEasyHack and EasyHack and to make queries much easier we are changing ProposedEasyHack to NeedsDevEval. Thank you and apologies for the noise
Migrating Whiteboard tags to Keywords: (needsDevEval) [NinjaEdit]
** 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
This bug still exists in 5.2.3.2 (Ubuntu 16.04, x86_64), in a slightly different form: Here is what I do step by step: 1. Open an Impress file. 2. Click on a custom animation. 3. Click the Remove button. If the slide was previously selected, the Add… button remains active. Otherwise, it is now greyed out. 4. If the Add… button was not greyed out by the previous step, Click the Add… button. 5. Nothing happens. (Previously, the Add… button was now greyed out.) To reactivate the Add… button, I need to click in the slide. Selecting an effect is not sufficient. However, if an Effect is selected, then I need to change to another slide and back to the current one in order to reactivate the Add… button. In short, the situation in 5.2 is more complicated and confusing than in 4.2, and the basic usability problem still exists.
** 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 still exists in 5.4.4 (Ubuntu 16.04, x86_64), in the same form as in 5.2.3.2. As I've commented before, I would be most grateful if the LibreOffice developers could find a way to not auto-expire bugs that are clearly not going away (perhaps that have been confirmed twice already in annual reviews?). In the last few years the bulk of my time interacting with the LO bug tracker has been spent simply confirming that already-reported bugs still exist. This is not a good use of my time, or of the time of developers who have to review this information.
Dear Reuben Thomas, 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 still exists in 6.0.7.3 (Ubuntu 18.04, x86_64), in the same form as in 5.2.3.2.
Dear Reuben Thomas, 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
Dear Reuben Thomas, 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
I tried reproducing this bug in 7.6.2.1, using the steps I provided in Comment #12. When I remove the custom animation, the "+ Add" is no longer greyed out. However, when I click on "+ Add", instead of just adding a new effect, it pastes a copy of the entire effects tree the slide originally had. I cannot work out how to simply add an effect. Maybe this even counts as a different bug?
(In reply to Reuben Thomas from comment #19) > I tried reproducing this bug in 7.6.2.1, using the steps I provided in > Comment #12. > > When I remove the custom animation, the "+ Add" is no longer greyed out. > However, when I click on "+ Add", instead of just adding a new effect, it > pastes a copy of the entire effects tree the slide originally had. I cannot > work out how to simply add an effect. Maybe this even counts as a different > bug? This is normal: it is because you have selected a text box containing multiple paragraphs/bullets. I tested it with slide 2 in attachment 80278 [details]. There is another corner case I found that was introduced in 6.1: bug 159241. Let's close this one.