Description: In the Find and Replace dialogue, the option 'Replace backwards' doesn't always keep its status (on or off) as set by the user. See examples below as steps to reproduce. It looks like an issue with the setting of a global variable/flag... Steps to Reproduce: First example: 1. Open Find and replace (Ctrl + H) 2. Fill in the fields for Find:... and Replace:... 3. Check the option 'Replace backwards' 4. Click 'Find All' --> 'Replace backwards' gets unchecked Second example: 1. Open Find and replace (Ctrl + H) 2. Fill in the fields for Find:... and Replace:... 3. Click 'Find Next' 4. Check the option 'Replace backwards' 5. Click 'Find Previous' --> 'Replace backwards' gets unchecked Third example: 1. Open Find and replace (Ctrl + H) 2. Fill in the fields for Find:... and Replace:... 3. Check the option 'Replace backwards' 4. Click 'Replace' 5. Uncheck 'Replace backwards' 5. Click 'Find Previous' or 'Find Next' --> 'Replace backwards' gets checked again Actual Results: 'Replace backwards' gets checked or unchecked by other actions than the manual toggling from the user. Expected Results: 'Replace backwards' should stay checked/unchecked when not toggled directly by the user. Reproducible: Always User Profile Reset: No Additional Info: [Information automatically included from LibreOffice] Locale: en-US Module: TextDocument [Information guessed from browser] OS: Linux (All) OS is 64bit: yes [LibreOffice install] Version: 6.3.2.2 Build ID: 1:6.3.2-0ubuntu0.18.04.1~lo1 CPU threads: 8; OS: Linux 4.15; UI render: default; VCL: gtk3; Calc: threaded
On pc Debian x86-64 with master sources updated today, I could reproduce this. Heiko/Xisco: I also think the checkbox shouldn't be changed automatically, any thoughts? Also, when I use key id locale, when open Find/Replace dialog, I got a key only for Paragraph Styles. Should I submit a new bugtracker about this?
Dear Alex, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug