When Ctrl+F is pressed to open Find bar, pressing of key combination left Ctrl+Alt+F opens File menu instead of Find&replace menu. Ctrl+Alt+F works if between those 2 manipulations cursor is pressed somewhere in text. Works in Calc and Writer. Right Ctrl+Alt+F do not cause any reaction at any conditions. I suppose it should be noted somewhere in help/description. By the way, is there reasonable way to close find bar using keyboard?
(In reply to comment #0) > When Ctrl+F is pressed to open Find bar, pressing of key combination left > Ctrl+Alt+F opens File menu instead of Find&replace menu. Ctrl+Alt+F works if > between those 2 manipulations cursor is pressed somewhere in text. Works in > Calc and Writer. I confirm Ctrl+Alt+F works only if cursor in is in the text with Find bar opened. > Right Ctrl+Alt+F do not cause any reaction at any conditions. I suppose it > should be noted somewhere in help/description. Right Ctrl+Alt+F works for me (same as Left key). I'm running on Windows Vista. Which OS did you used ? > By the way, is there reasonable way to close find bar using keyboard? With the cursor in the Find bar, press Escape.
Ubuntu 10.04.2 x86 LO 3.4 >When Ctrl+F is pressed to open Find bar, pressing of key combination left >Ctrl+Alt+F opens File menu instead of Find&replace menu. Ctrl+Alt+F works if >between those 2 manipulations cursor is pressed somewhere in text. Reproduced. Ctrl+Alt+F does nothing if cursor in the find bar. >Right Ctrl+Alt+F do not cause any reaction at any conditions. NOT reproduced.
> Right Ctrl+Alt+F works for me (same as Left key). > I'm running on Windows Vista. Which OS did you used ? > Ubuntu 10.10 > > > By the way, is there reasonable way to close find bar using keyboard? > > With the cursor in the Find bar, press Escape. Thank you for that!
By the way, it is not possible to only Find using Match Case or Whole Words Only or any of the other options. Users must guess that they have to invoke the Find and Replace dialog even though they don't need the Replace function. That's not exactly intuitive. If I want to do a case-senstive Find I should be able to open the dialog with Control-F and select that option. As it is now, Control-F takes me to the Find toolbar which cannot be disabled. [Tested in Windows XP, LibreOffice 3.4.2]
Mwah, there may be so much that does not work when the find bar has the focus. Is this really a bug?
(In reply to comment #4) > By the way, it is not possible to only Find using Match Case or Whole Words > Only or any of the other options. Users must guess that they have to invoke the etc. Hi Charles, The interaction of options set with the working find bar, already is mentioned in other issues.
[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
reproduced this: if cursor placed in any toolbar, no keyboard short-cuts work reproduced in LibO 3.6.0 master on Fedora 64 bit
*** Bug 45903 has been marked as a duplicate of this bug. ***
reproducible with LO 4.3.2.2 (Win 8.1) If the cursor placed in any toolbar, no shortcut key works. But Ctrl+Alt+F is in my LO release no shortcut for the FIND & REPLACE dialog. The shortcut for this dialog is Ctrl+H.
** 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
still the case
*** Bug 64341 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 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
*** Bug 119666 has been marked as a duplicate of this bug. ***
https://gerrit.libreoffice.org/66377
Mike Kaganski committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/+/c977473546e450ec122f5d3dbc4578d8994962ef%5E%21 tdf#38328: allow Find&Replace key combinations in FindTextFieldControl It will be available in 6.3.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.