Bug 36582

Summary: "Find and replace" finds/replaces text deleted with "record/track changes"
Product: LibreOffice Reporter: Tomasz Kucza <magnesus2>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: NEW --- QA Contact: chuck598 <chuck598>
Severity: normal    
Priority: medium CC: anistenis, gleppert, mst.fdo, stfhell
Version: 3.4.4 release   
Hardware: All   
OS: Linux (All)   
URL: chuck598@gmail.com
Whiteboard:
i915 platform: i915 features:
Bug Depends on: 23631    
Bug Blocks:    

Description Tomasz Kucza 2011-04-25 06:41:49 UTC
If you turn on recording and showing changes in document find and replace will replace even things already deleted. Example:

1. Create new document.
2. Write "This is a document".
3. Turn on showing and recording changes.
4. Delete the word "document" so you have "This is a".
5. Replace document with "file".
6. The document will contain: "This is a file." instead of "This is a".
Comment 1 Tomasz Kucza 2011-04-25 06:43:03 UTC
PS. In point 5 I mean "Use search and replace to change word 'document' to 'file'". Sorry for being vague.
Comment 2 gleppert 2011-04-25 11:19:23 UTC
I tested the bug as described. I can confirm the bug on my system. 

Furthermore, the bug is even more serious than described:

* First problem as described by Tomasz: The replace deleted word is active/undeleted after search&replace. This actually destroys the written text.

* Second problem: After hitting "Replace all" a couple of times, it will keep replacing the deleted text with the new text. The dialog never displays "Word not found" and hence does not stop.

Due to the reason that data can be actually made unusable/unreadible, I change the importance to high/major. I hope this is okay. 

System: Ubuntu 10.4./Gnome,  LibreOffice 3.3.2 PPA, Intel 32Bit
Comment 3 Björn Michaelsen 2011-12-23 12:07:33 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 4 chuck598 2012-02-11 19:30:57 UTC
No longer does find & replace work for me.

I have deleted LibeOffice & reinstalled & no change.

Maybe there is a report that I didn't see about this or maybe only me?

I am only a user so not to good & this as this is the first time I have tried to report a problem.
Comment 5 gleppert 2012-03-19 09:45:16 UTC
This severe regression is still there in LibreOffice 3.5.
I just 'destroyed' a document myself where track changes was activated (and extensively used) and I wanted to search&replace something.

Please increase the severity of this bug!
Comment 6 stfhell 2012-10-15 19:55:15 UTC
Still a problem in LO 3.6.2.2. In summary: When "Show tracked changes" is active, "Find" will find text that has been deleted with "track changes" activated. "Find & replace" will replace already deleted text. When you do "Find & replace" with activated "track changes", it will replace the same (already deleted) text again and again. "Replace all" works insofar as it replaces each occurance only once.

Actually it can be useful if "Find" also searches tracked deletions - after all you use "track changes" to be able to keep deleted text in the document. But I think it's usually not what you want. So you would have to disable "show tracked changes" just to do a "Find". I cannot imagine a situation where you would like already deleted text to be replaced by newly inserted text.

It's definitely a bug that LO does not at least move the cursor behind the replaced text when you choose "Replace" in the "Find & replace" dialogue with "track changes" activated. That leads to the same text being replaced again and again.
Comment 7 Michael Stahl 2012-12-18 17:22:53 UTC
please somebody tell me which OOo/LO version did not have this bug.

i can reproduce it going back to OOo 3.0.1, so doesn't look like a regression.
Comment 8 stfhell 2012-12-18 20:08:47 UTC
I can't remember that this has ever worked differently. The corresponding OOo bug was filed in 2007 for OOo 2.3:
https://issues.apache.org/ooo/show_bug.cgi?id=82591
Comment 9 Björn Michaelsen 2014-02-28 12:45:56 UTC
Bulk change: Bibisected bugs can be assumed to be regressions.
Comment 10 Michael Stahl 2014-02-28 12:49:27 UTC
removing erroneously added "regression", see comment #7
Comment 11 Xisco Faulí 2014-07-30 09:46:46 UTC
According to comment 7 this isn't a regression, thus remove bibisected35
bibisected35older from whiteboard

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.