The search result message is partly displayed over the toolbar. In my case I have the FIND toolbar enabled (VIEW -> TOOLBARS -> FIND) and then you will find it in the toolbar at the bottom. Steps to Reproduce: 1. Open WRITER 2. Enter a search term not available in the document and press the ENTER key or the Arrow Down icon next to the search field (the second arrow not the arrow for the pop-up window) Result: If the search term is not available you get the message "Search key not found", but this message is badly visible, because it overlays the search field. 3. Now change the search term to another not available character/word and search for it or press ENTER / Arrow Down key a second time without changing the search term or also without changing the search term switch for instance to your browser and then back to CALC Result: You see/get again the message "Search key not found", but this message is mostly not visible, because it is overlaid by the search field. The problem is the same if the character/word can be found in the document when the end of the document is reached and you get the message "Reached end of the document". reproducible with LO 4.3.2.2 (Win 8.1)
Hi Andy, Reproduced with LO 4.3.2.2 Build ID: edfb5295ba211bd31ad47d0bad0118690f76407d & Windows 7 Home Premium This was not the case for LO 4.3.2.1 Build ID: f9b3ad49d92181b0a1fe7e76f785a2c2cd0847d3 So regression. Regards, Jacques
Migrating Whiteboard tags to Keywords: (notBibisectable)
This regression was introduced before branch 4.4, thus it can't be bibisected with the current bibisect repositories. Changing keyword 'notBibisectable' to 'preBibisect'
** 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.4.1 or 5.3.6 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-20170929
I think Jim Raykowski's work has fixed this, but I was unable to quickly find the matching commit/issue.