Description: when you search for a string in a document and there's zero result, it is not obvious enough that there's no point in hitting enter again... and I'll hit enter again, hoping that now the search will start from the beginning... like in Geany, if I'm not mistaken... in any case, Firefox is a very good example... when a search string does not exist, the search field will be red... making it obvious that it does not exist... Writer, no doubt, makes it obvious, too, by displaying "search key not found" in the status bar, at the far right... it's just the farthest place to look at... if one reds left to right, top to bottom the worst thing, however is, which could be easily eliminated, that when hitting enter again, the cursor will jump to the beginning of the document... this is really an annoying behavior Steps to Reproduce: 1. search for a string that has zero appearances in a document 2. hit enter 3. hit enter again Actual Results: the cursor will jump to the beginning of the document Expected Results: the cursor should stay where it was.. and.. in some intuitive way, the fact that the "search key was not found" could be emphasized... like turning the search field red, for example... Reproducible: Always User Profile Reset: No Additional Info: next to the search field the number of matches could be displayed, too.. like 0 matches, 14 matches... this could help handling the situation already... including using or not even trying to use the up and down arrow icons (to navigate through the matches) - - - thank you for developing LO Writer - - -
Peter, I assume, you're talking about find & replace dialog. In find toolbar the string becomes red, if there's no hit. So this is like you expect. In Find & Replace dialog the string becomes red also, but since it is still highlighted, you don't see it. So I also think, it would be nice, if this string is no longer highlighted, if there is no search result. Would this solve your problem, Peter? => NEEDINFO
Dear peter josvai, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
Dear peter josvai, Please read this message in its entirety before proceeding. Your bug report is being closed as INSUFFICIENTDATA due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided): a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present b) Provide easy to reproduce steps – the simpler the better c) Provide any test case(s) which will help us confirm the problem d) Provide screenshots of the problem if you think it might help e) Read all comments and provide any requested information Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. Please do not: a) respond via email b) update the version field in the bug or any of the other details on the top section of our bug tracker Warm Regards, QA Team MassPing-NeedInfo-FollowUp