Bug 125663 - After "replace all" only the part of the string is selected
Summary: After "replace all" only the part of the string is selected
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.1.0.3 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: implementationError
Depends on:
Blocks: Find-Search
  Show dependency treegraph
 
Reported: 2019-06-03 16:59 UTC by raal
Modified: 2022-07-04 03:27 UTC (History)
4 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 raal 2019-06-03 16:59:03 UTC
Description:
follow-up of bug 44837 

Steps to Reproduce:
write  bsdbsd
select all
find and replace: b > a ; current selection only

Actual Results:
after "replace all" only the string "sdasd" is select

Expected Results:
string "asdasd" should be selected.


Reproducible: Always


User Profile Reset: No



Additional Info:
printscreen http://bugs.documentfoundation.org/attachment.cgi?id=151770
Comment 1 raal 2019-06-03 17:00:02 UTC
Xisco confirmed, setting as new
Comment 2 Xisco Faulí 2019-06-10 13:57:39 UTC
Yep, confirmed in

Version: 6.4.0.0.alpha0+
Build ID: 43ddddb703bcdb9430752af63ae46527f737f874
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3; 
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded
Comment 3 Aron Budea 2020-06-07 01:36:38 UTC
Still in 7.1.0.0.alpha0+ (8aee8c0cf1bdda1866594e75b0f9bd4b9a69c724).
Started with 5.1.0.3, in 5.0.0.5 the text is deselected after replace.
Comment 4 Andreas Heinisch 2020-07-03 12:47:52 UTC
The problem appears in DocumentContentOperationsManager::ReplaceRangeImpl in https://opengrok.libreoffice.org/xref/core/sw/source/core/doc/DocumentContentOperationsManager.cxx?r=682e0488#4279 where the positions get corrected in https://opengrok.libreoffice.org/xref/core/sw/source/core/doc/doccorr.cxx?r=0f097b4d#58, but the poblem exceeds my knowledge how to fix this behaviour.
Comment 5 QA Administrators 2022-07-04 03:27:38 UTC
Dear raal,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

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

Warm Regards,
QA Team

MassPing-UntouchedBug