I noticed this on the Options toolbar in Draw. Some toolbar buttons are Boolean option selections that look "pushed in" when the option is enabled. Issue: there is too much delay from when the user clicks the button to when the button toggles its status. This can cause the user to click the button several times rapidly, on the assumption that the first click may not have registered. This can cause the button to toggle its state a couple of times after the user stops clicking; this can be further annoying. LibreOffice 4.1.4.2 on Ubuntu 13.04. I'm using the "libreoffice/ppa" PPA from launchpad.net.
Hi. Thank you for your report. It deals with the great subject of UI reactivity. The facts are that : - the modern "fat" softwares perform tons of calculations, UI updates, etc. at each user interaction, - the reactivity depends on the power of PCs, their workload (multiple software running at the same time ; or CS architecture like CITRIX), and the design of the observed software (LibreOffice here). A trade-off must be found between : - a less multi-threaded design, wich ensure good synchronisation between all part of the software (UI and internal state, for instance), at the price of a slow reactive UI, - a more multi-threaded design, which leads to complex bugs, often impossible to reproduce, due to the accepted desynchonisation (see bug 73829 comment 3). In the current case, it is not very difficult to make the button toggling exactly at the time it is depressed, but an unavoidable calculation time is needed to set accordingly the internal state of the (rich, large) LibO software. Not all users have very powerful workstations. Status kept to UNCONFIRMED, to get additionnal advices.
Ubuntu 14.10 x64 LibreOffice 4.4.0.3 release LibreOffice 3.3 (updating version to reflect that this bug came from OpenOffice days). Note that version reflects oldest version that the bug is confirmed on - comments are used to say that the bug still exists on a currently supported version. Confirmed Marking as: New Trivial - virtually has no impact - the delay is less than 1 second. Even if a user is impatient, they'll quickly learn what's going on and hopefully slow down by 1 second when they click an option. Lowest - default for trivial bugs - seems appropriate.
** 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.0.5 or 5.1.2 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
** 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.2.7 or 5.3.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-20170522
Adding needsUXEval to discuss this issue. Is this still relevant? My take is this is a WFM or a NAB.
Ping to ux-advice (Thomas' is a ninja)
(In reply to Thomas Lendo from comment #5) > Adding needsUXEval to discuss this issue. > > Is this still relevant? My take is this is a WFM or a NAB. Let's close as WFM.