Bug 68079 - Writer: Issues searching inside a frame that contains a table
Summary: Writer: Issues searching inside a frame that contains a table
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
3.3.0 release
Hardware: Other All
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-13 19:01 UTC by crxssi
Modified: 2016-04-18 05:27 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
sample document (8.52 KB, application/vnd.oasis.opendocument.text)
2013-08-13 19:01 UTC, crxssi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description crxssi 2013-08-13 19:01:38 UTC
Created attachment 84026 [details]
sample document

Searching inside a frame that contains a table will not "wrap around" the search on subsequent search operations.

The bug is apparently ancient.  I found it in LO 4.1.0, but when tested under OO 3.0.1 it was still there, and it might be older than that.  3.3.0 is the oldest option LO.

Steps to recreate:

* Go into writer and create a document
* Create a frame (Insert->Frame) of any type
* Position in the frame
* Create a table inside the frame of any size (Insert->Table)
* Type a word in one of the cells
* Activate find [search] (Edit->Find)
* Type in the word you entered in the cell and press the "Find" button
* It will find and highlight the word you entered in the cell
* Press the "Find" button again
* It will say "LibreOffice Writer has searched to the end of the document.  Do you want to continue at the beginning?"  Click on "Yes"
* It will NOT find the word again, no matter how many times you try the Find function.  Not until you position the cursor somewhere OUTSIDE the frame (even clicking outside the table inside the same frame will not reset it).

If your document is complex, this search behavior is very frustrating, unfriendly, and essentially lies to the user.

Just to make things faster to diagnose, I am attaching a sample document that can be used for the test, but creating your own sample only takes a moment.
Comment 1 tommy27 2013-08-20 16:58:00 UTC
confirmed under Win7 64bit. inherited from OOo. setting version to 3.3.0 (first LibO release).
Comment 2 QA Administrators 2015-04-01 14:40:12 UTC
** Please read this message in its entirety before responding **

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 on a currently supported version of LibreOffice (4.4.1 or later)
   https://www.libreoffice.org/download/

   *If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
 
   *If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

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)

http://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: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-04-01
Comment 3 tmacalp 2015-04-06 15:13:44 UTC
This bug is still valid in LibreOffice 4.4.1 under 32bit Fedora 17.

To expand on the behavior a bit, here are two other characteristics of this bug:

1. The table inside the frame is unnecessary.  This behavior can be reproduced with just a simple frame.  Insert a frame and type the desired search phrase in it a couple times.

2. This bug is not triggered if the search phrase also exists outside of the frame.

It appears that the problem is when it attempts to wrap around, it sets the cursor in the wrong place.  You can see an example of this by doing the following:

* Create a new document
* Insert a frame
* Click in frame
* Type "this"
* Press Enter
* Type "this" again
* Click outside of frame

Now comes the fun stuff.
* Ctrl-f and search for "this" (finds first instance)

* Find next (finds second instance)

* Find next (returns "Search key not found", but also note that the cursor is now at the beginning of the FRAME, not the beginning of the document.)

* Find next (finds first instance)

* Find next (finds second instance)

* Find next (returns "Search key not found", but also note that the cursor is at the END of the document.

* Now, no subsequent "Find next" will return a result.
Comment 4 tommy27 2016-04-16 07:26:17 UTC
** Please read this message in its entirety before responding **

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 on a currently supported version of LibreOffice (5.0.5 or 5.1.2 https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior
 
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

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)

http://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: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2016-04-16
Comment 5 tmacalp 2016-04-18 02:56:53 UTC
I can no longer reproduce this bug.  There have been quite a few changes to the search toolbar and it appears that one of them took care of this bug.  Of course, it appears the new search toolbar comes with a handful of other bugs to report( no wrap-around message, "placeholder for message" [probably for wrap around message], find prev/next buttons greyed out when toolbar dismissed/reenabled)

Tested under
Version: 5.1.2.2.0+
Build ID: 5.1.2.2 Arch Linux build-1
CPU Threads: 6; OS Version: Linux 4.5; UI Render: default; 
Locale: en-US (en_US.UTF-8)

I'll leave it to someone else to confirm that it's fixed and I guess it should be closed as worksforme since we don't know which commit fixed it.
Comment 6 tommy27 2016-04-18 05:27:22 UTC
@tmacalp
since you were one of those who experienced this bug, I think it's enough to mark it as WFM

regarding the other issues you mentioned, please open new bug reports about them