Issue 2236 - 'Find backwards' highlights all but last character of the word being found.
Summary: 'Find backwards' highlights all but last character of the word being found.
Status: CLOSED FIXED
Alias: None
Product: Writer
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.1
Hardware: PC Windows 2000
: P3 Trivial (vote)
Target Milestone: ---
Assignee: christian.guenther
QA Contact: issues@sw
URL:
Keywords: oooqa
: 6486 6527 (view as issue list)
Depends on:
Blocks:
 
Reported: 2001-11-18 19:45 UTC by Unknown
Modified: 2013-08-07 14:43 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2001-11-18 19:45:16 UTC
When attempting to find an existing word backwards (Find with the 
option 'Backwards' checked), Presentation highlights all but last character of 
the word being found.

Steps to reproduce:
1. Drag and drop a text box.
2. Enter "Winners never quit".
3. Click 'Edit' from the menu and click 'Find&Replace'.
4. Enter "never" in the 'Search for' input box. Make sure that 'Backwards' is 
the only option checked.
5. Click the 'Find' button.

Actual Result:
"neve" was highlighed.

Expected Result:
The word "never" should be highlighed.

Build date and Platform:
10/1/01 build Windows 2000 5.0.0.2195 Service Pack2.

Follow up test:
1.  The same steps were repeated to find the first word of the sentence 
i.e. "Winners". Interestingly, all the letters of the sentence except "Winner" 
were highlighted.

2. The same steps were repeated to find the last word of the sentence 
i.e. "quit". "qui" was highlighted exposing the same defect mentioned in the 
Summary.
Comment 1 cemkaner 2001-11-23 10:00:45 UTC
Cem Kaner (kaner@kaner.com) 11/23/01--I replicated this problem on build 638c, on a Win2K system. 
Similar effects with searches for other words (e.g. OpenOffice, search for OpenOffice and it 
highlights the trailing e.)
Comment 2 bettina.haberer 2001-11-26 15:12:51 UTC
Reassigned to Christian.
Comment 3 christian.guenther 2001-11-27 11:21:44 UTC
I can reproduce the bug in the latest internal accessable version.
Comment 4 Dieter.Loeschky 2001-12-03 09:56:16 UTC
DL: Bug 95297.
Comment 5 Dieter.Loeschky 2002-03-25 08:31:31 UTC
DL->KA: I think it might be your task.
Comment 6 ooo 2002-04-02 14:43:13 UTC
I'll take a look.
Comment 7 prgmgr 2002-07-21 16:57:40 UTC
Problem also exists inside the Writer program.

Linked a duplicate issue 6468.

Duplicated on Win NT 4.0, OO 1.0.1
Comment 8 prgmgr 2002-07-21 16:58:55 UTC
*** Issue 6486 has been marked as a duplicate of this issue. ***
Comment 9 prgmgr 2002-09-26 02:54:05 UTC
*** Issue 6527 has been marked as a duplicate of this issue. ***
Comment 10 prgmgr 2002-09-26 03:25:20 UTC
I'm changing this issue from 

ka@openoffice.org, issues@graphics.openoffice.org

to

sba@openoffice.org, issues@sw.openoffice.org

Sorry if I got this wrong.

In my basic tests, I don't see this problem happening in Impress or 
Calc.

I can reproduce this behaviour in Writer.

Change this issue to a P2 priority since the Replace feature of the 
Find and Replace function depends on the correct text being selected.
Comment 11 stefan.baltzer 2002-11-28 16:43:06 UTC
Gordon, KA is a developer. Leave it in his hands :-)
Comment 12 ooo 2002-12-02 11:24:18 UTC
KA=>AF: AFAIK this bug (Draw/Impress) has already been fixed by you? I
don't know the state of the Writer Search&Replace functionality.
Comment 13 groucho266 2002-12-02 15:22:48 UTC
I can't reproduce the bug as described but am aware of backward
searching working not so well (it is not implemented at all in
Impress; only in single objects selected by hand this is possible). 
However, this problem should be fixed with the fix for task #95297#.
Comment 14 groucho266 2003-01-10 12:45:38 UTC
I checked that the bug is fixed in SRX644 a.
Comment 15 groucho266 2003-01-10 12:47:10 UTC
As said before, the bug is fixed in SRX644 a.
Comment 16 christian.guenther 2003-01-10 13:12:46 UTC
Verified in the latest internal version. The fix is included in the
next developer build.
Comment 17 christian.guenther 2003-01-10 13:13:03 UTC
I close the issue.