Created attachment 102942 [details] screenshot of setup Problem description: When doing a Search and Replace All, with Regular expressions and Current selection only selected, after Replace All, Current selection is deselected Steps to reproduce: 1. Select column of text with valid entries 2. Select Find and Replace 3. Put in a regex: ([0-9]+) replacing with $1;GPS. 4. Select Regular expressions and Current selection only 5. Search and replace Current behavior: (Sometimes) after replace happens and I select the next column to do the operation on, the "Current selection only" becomes deselected. So the whole document starts replacing any number string (which can crash Calc). Expected behavior: Maintain selected preferences in Find and Replace Notes: Not consistent behavior. Sometimes it works and other times not. Try is several times first? Operating System: Mac OS X Version: 4.1.6.2 release
(In reply to comment #0) > .... > > Notes: Not consistent behavior. Sometimes it works and other times not. Try > is several times first? > reproduced one time with LibO 4.2.5.2 under Win7x64 not reproducible in a consistent way like you said please upload a test spreadsheet file so other may easily test
Created attachment 102997 [details] Test case
Created attachment 102998 [details] Video Example So the Current selection becomes deselected when making new selections, not doing the find and replace. So to reproduce the issue, just make Current selection be selected, then select different areas of the document.
I got consistent behavior with this simple steps: 1. Open attached file 2. Select any cell ranges 3. Find and Replace (ctrl-H) 4. Click 'Other Options' and verify that "Current selection only" ticked 5. Select any cell ranges outside previous selection Reproduced with LO 4.3.0.3, 4.0.6.2, 3.6.7.2, 3.3.0.4 - Ubuntu 12.04 x86 AOO 3.4.1 and 4.1.0 doesn't select "Current selection only" by default, but the check box greyed out with above steps. So this behavior likely inherited from OOO.
** 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.5 or 5.2.1 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-20160920
*** Bug 113813 has been marked as a duplicate of this bug. ***
Still reproducible in Version: 6.3.0.0.alpha1+ Build ID: f897342320ad3a29cf4be1437c8e3ce888bdb3cb CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US Calc: threaded
i could NOT ENCOUNTER the bug after several tries. everything works as expected. I did my tests in the file "Test Case" provided by Nick in the Attachments. Version: 7.1.0.3 / LibreOffice Community Build ID: 10(Build:3) CPU threads: 4; OS: Linux 5.10; UI render: default; VCL: kf5 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Dear Nick, 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
FWIW, as of 7.6.alpha, the "Current selection only" checkbox keeps the check-mark when changing the selection, _if_ the new selection is still "relevant". For instance, using attachment 102997 [details] from comment 2: 1. Select column B 2. [CTRL]+[H] 3. Select column C > check-mark still ON. 4. Select cell A1 > check-mark still ON. 5. Select column D, which is empty > check-mark is now OFF. 6. Select column A > check-mark still OFF. The checkbox is automatically set OFF when the highlighted area has no content. Someone could claim that when re-selecting a "possibly-relevant" area, then perhaps the check-mark should automatically turn ON again. But for that, a series of conditions would need to be true, and I'm not sure every possible condition or context would be predictable (or IOW, to predict what the user is about to do and what its real intention).
Unifying in one bug. *** This bug has been marked as a duplicate of bug 132031 ***