Bug 157744 - find is hampered by settings in find/replace
Summary: find is hampered by settings in find/replace
Status: RESOLVED DUPLICATE of bug 115665
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.5.6.2 release
Hardware: All Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Find-Toolbar
  Show dependency treegraph
 
Reported: 2023-10-13 15:57 UTC by Tracey
Modified: 2023-10-27 13:11 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tracey 2023-10-13 15:57:03 UTC
If I use find/replace with search criteria, but forget to clear the criteria when done, the criteria is applied to find even though find only shows find-all and match-case as search options.

Please disconnect the find/replace criteria from the find function.

Thanks, Tracey
Comment 1 V Stuart Foote 2023-10-13 19:21:35 UTC
For OP, please provide build and os details from the Help -> About dialog.

Also, seems related to bug 62601 (and dupes) where this was resolved, could you please provide specific steps to reproduce your issue of bleed-over to the Find-bar from the Find-and-Replace dialog.
Comment 2 V Stuart Foote 2023-10-13 19:25:22 UTC
depending on the STR OP provides may be dupe of bug 115665
Comment 3 Tracey 2023-10-14 15:57:07 UTC
I use search/replace specifying a text with a particular font (or any restrictive characteristics).

When I exit search/replace then try to find some text, if it fails to find something I know is there, I have to go back into search/replace and click on "no format".

After that, the find function works fine.

Thanks, Tracey

Version: 7.5.6.2 (X86_64) / LibreOffice Community
Build ID: f654817fb68d6d4600d7d2f6b647e47729f55f15
CPU threads: 2; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL threaded
Comment 4 QA Administrators 2023-10-15 03:16:45 UTC Comment hidden (obsolete)
Comment 5 Buovjaga 2023-10-27 13:11:25 UTC

*** This bug has been marked as a duplicate of bug 115665 ***