Currently, the "Find" toolbar contains a "Match Case" checkbox item. However, check boxes should never be used in a toolbar -- buttons should be used instead (in the same way that "Bold", "Italicize", and "Underline" are buttons, not checkboxes). Please convert any toolbar checkboxes, including the "Match Case" one, to buttons.
would you please post a screenshot?
(In reply to comment #1) > would you please post a screenshot? @tommy, Mirek is talking about the "Match case" checkbox when you "CTRL+F" in writer. @Mirek: I dont think this is a bug. A button is an action (it applies bold/Italicize/underline to text/paragraph). A checkbox is an option (For the "match case" one, it tells the "find" action that you want to match case when you find) It makes no sense to convert the "match case" to a button. How can it be implemented? what's the advantage?
Exactly like the Bold button does, like Visual Studio editor does, etc.
(In reply to comment #2) > (In reply to comment #1) > > would you please post a screenshot? > > @tommy, Mirek is talking about the "Match case" checkbox when you "CTRL+F" > in writer. > > @Mirek: I dont think this is a bug. > A button is an action (it applies bold/Italicize/underline to > text/paragraph). > A checkbox is an option (For the "match case" one, it tells the "find" > action that you want to match case when you find) > It makes no sense to convert the "match case" to a button. How can it be > implemented? As a button, which shouldn't really be that hard, considering buttons are a toolbar's specialty and . If you'd like to see an actual implementation, take a look at the Find bar: Firefox (25+). A screenshot from the web: https://3.bp.blogspot.com/-0lhD-hxtbw4/UkMjVSy2KVI/AAAAAAAAAKA/5iFxZoeu3zE/s1600/findbar1.png > what's the advantage? Well, it's mostly superficial. Labels of checkboxes in toolbars right now don't have the same size as button labels and that makes toolbars with both look inconsistent. (I'll attach a screenshot.) Secondly, it has to do with perceived target area. Because checkbox labels aren't always actionable, the perceived target area may for some users be just the check box and not its label. With a button, it's clear that the whole button is actionable.
Created attachment 103472 [details] Current LO find bar
Created attachment 103473 [details] Current LO find bar
*** Bug 83321 has been marked as a duplicate of this bug. ***
*** Bug 83329 has been marked as a duplicate of this bug. ***
** 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.1 or preferably 5.0.2.2 or later) 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: 2015-10-14
The enhancement request still stands and is valid, but I’m not convinced of its alleged advantages (on the “perceived click area”) anymore – not that I were ever actually very convinced of it.
** 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-20161108
Heiko, what do you think about this "problem"?
(In reply to Roman Kuznetsov from comment #12) > Heiko, what do you think about this "problem"? It's true that toolbars must not contain of other controls but buttons. But guidelines also must not be strict and exceptions should be allowed. The Find toobar is such a case: a temporary toolbar, clear interaction, known for long. So we better set this issue as WFM.