https://bugs.documentfoundation.org/show_bug.cgi?id=36582
--- Comment #29 from Lars Jødal <l...@rn.dk> --- (In reply to NISZ LibreOffice Team from comment #23) > Created attachment 159953 [details] > Screenshot of Word and Writer side by side after following the steps > > Still happens in: > > Version: 7.0.0.0.alpha0+ (x64) > [...] > > Also: this behavior is the same as in Word. As noted by NISZ LibreOffice Team, the behaviour is very much similar i Word: Also in Word, Search & Replace while showing track-changes, does search within deleted text and replaces with non-deleted text. Just tested with MS Office 365. I can see why it can sometimes be relevant to search also in deleted text, e.g. to find where you (or a colleague) deleted something. And if you do not want this, just turn off showing track-changes. But I fail to see why anybody would want already-deleted text to be part of replacing. (Even before the problems of doing more than one search & replace, leading to several instances of the new text.) Well, failing the see the use could be just my lack of imagination. So: Can anybody come up with a case where searching within deleted text and replacing with new text would be the intended behaviour? Put another way: Can anybody see a reason why this would NOT be a bug (happening to be shared by LO and MS Office)? PS: Word notes the user that "We are through searching the document" after one pass, so the user will at least know that if s/he continues replacing, it will be in text that had already been considered. This will stop most users from repeated replacement, but does not change the question how replacing at all in deleted text could be the intended behaviour. -- You are receiving this mail because: You are the assignee for the bug.
