Bug 148933 - Find and replace does not function as expected or consistently
Summary: Find and replace does not function as expected or consistently
Status: RESOLVED DUPLICATE of bug 148840
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
7.2.5.2 release
Hardware: All Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-04 16:07 UTC by Randy
Modified: 2022-05-04 18:42 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
Document most recently used when bug happened again. (19.35 KB, application/vnd.oasis.opendocument.text)
2022-05-04 16:09 UTC, Randy
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Randy 2022-05-04 16:07:07 UTC
Description:
The find function does not find all occurrences when extra formatting is applied.  Selecting "match case" works properly, but when I add formatting to the search parameters, the find function does not find all occurrences.  I will try to attach a sample document.

Steps to Reproduce:
1.use find and replace to find C# in the document and replace with D.  Select "match case".  All occurrences are found.
2.Use find and replace to find C# in the document and replace with D.  Select "match case".  Also choose formatting options - Font: Times New Roman  Weight: Bold  Size: 12pt.   This time only one occurrence found, even though there are many more.
3.

Actual Results:
Depending on the letter searched for, more or less instances are found but not all.

Expected Results:
All results should be found with set paramaters.


Reproducible: Always


User Profile Reset: No



Additional Info:
[Information automatically included from LibreOffice]
Locale: en-US
Module: TextDocument
[Information guessed from browser]
OS: Windows (All)
OS is 64bit: no
Comment 1 Randy 2022-05-04 16:09:36 UTC
Created attachment 179922 [details]
Document most recently used when bug happened again.

I attached this document so the steps I have used could be repeated and hopefully determine the source of the error.
Comment 2 Martin Srdoš 2022-05-04 18:42:53 UTC

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