Bug 64315

Summary: EDITING: Find and replace odd behaviour with Edit > record and show changes
Product: LibreOffice Reporter: Steve <drgrumpy>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: cno, drgrumpy, jorendc
Priority: medium    
Version: 4.0.2.2 release   
Hardware: Other   
OS: Linux (All)   
Whiteboard: BSA
Crash report or crash signature: Regression By:

Description Steve 2013-05-07 11:03:25 UTC
Problem description: 
Find and Replace behaviour

Steps to reproduce:
1. Select Find and Replace
2. Enter Find and Replace terms
3. Click Replace
4. Click Replace again
5. Repeat

Current behaviour:
First click replace finds first instance
Second click replaces the text
Subsequent clicks repeatedly replace the first found text

Expected behaviour:
First click replace finds first instance
Second click replaces the text
Subsequent clicks find and replace the next instances of text to be replaced.

e.g. find: spp. replace species
click replace ~5 times
text: bla bla bla spp. bla bla bla spp.
result: bla bla bla speciesspeciesspecies bla bla bla spp.

I never noticed this in previous versions (e.g. last version I used was 3.6 I think)







              
Operating System: Ubuntu
Version: 4.0.2.2 release
Comment 1 Thomas van der Meulen [retired] 2013-05-09 09:13:57 UTC
Thank you for your bug report, I can't confirm this bug running LibreOffice 4.0.3.3 on Mac os x 10.8.3. 

wen pres Replace for the second time it replaces the first "spp" then I clicked it two more times it just replaces the last "spp" 

so my result will be: bla bla bla species. bla bla bla species. 
and it doesn't find any more matches.
Comment 2 Jorendc 2013-05-16 16:36:16 UTC
@Steve:

Is it possible to reset your user profile following this guide: https://wiki.documentfoundation.org/UserProfile#Resetting_the_user_profile ?
If still reproducible, can you retest using LibreOffice version 4.0.3.3 ?

Does that solve this issue?

Kind regards and thanks for retesting,
Joren
Comment 3 Steve 2013-05-17 18:17:55 UTC
Thanks for the attention.

I re-set the user profile and this makes no difference.... BUT I have some further info - it seems it is related to 'record' and 'show' changes.

So if changes are recorded and shown, then the original text displays with strikethrough and the first instance (struckthrough) gets repeatedly replaced, but if I uncheck show changes I get the expected behaviour. 

So it seems that the work around is to turn off show changes whilst doing a replace, then turn back on afterwords. I guess under the hood the replace needs to exclude struck-out text ?

Steve
Comment 4 QA Administrators 2013-12-22 21:59:15 UTC
Dear Bug Submitter,

This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/NEEDINFO

If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed.


Thank you for helping us make LibreOffice even better for everyone!


Warm Regards,
QA Team
Comment 5 QA Administrators 2014-02-02 02:00:50 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and a lack of information which is needed in order to accurately reproduce and confirm the problem. We encourage you to retest your bug against the latest release. If the issue is still present in the latest stable release, we need the following information (please ignore any that you've already provided):

a) Provide details of your system including your operating system and the latest version of LibreOffice that you have confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED and we will attempt to reproduce the issue. 
Please do not:
a) respond via email 
b) update the version field in the bug or any of the other details on the top section of FDO