143180 - MFCEmbed - "Match whole word only" in Find doesn't work

Status: RESOLVED DUPLICATE of bug 269442

(Core Graveyard :: Embedding: APIs, defect)

Description

[amutch]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.0.0+) Gecko/20020508
BuildID:    MFCEmbed - 5/8/2002 nightly build 

The "Match whole word only" option in the Find dialog does not work properly. 

Reproducible: Always
Steps to Reproduce:

1. Open any web page
2. Hit Ctrl-F to bring up the Find dialog
3. Check the option "Match whole word only"
4. Enter any sequence of chars that appear inside a word on the web page (eg.,
"stone" which appear inside the word "milestone")
5. Click on Find Next until your find ends "inside" the word (ie., until youf
find the "stone" part of the word "milestone")


Actual Results:  MFCEmbed matches every instance of the word, even when it is
inside a word.

Expected Results:  MFCEmbed should only match whole word matches of the word.

Comment 1

[R.K.Aa.]

judging by bug 14871, this has never been implemented?

Comment 2

[amutch]

This has not been implemented in Mozilla. However, it is implemented in MFCEmbed
so it affects embedding apps.

Comment 3

[Adam Lock]

-> Chak

Comment 4

[Chak Nanga]

Cc:ing Conrad for additional info.

Comment 5

[Conrad Carlen (not reading bugmail)]

  A long time ago, embedding samples (not sure about MfcEmbed but this was true
for PPEmbed) used a hand-rolled find impl that supported "entire word"
searching. When everything was moved to nsIWebBrowserFind and the impl of that
was changed, we lost the feature of "entire word" searching :-( It's in the
nsIWebBrowserFind API, but it doesn't do anything.
  So, and this is why I cc'd akkana ;-), what we really need is to support
entire word searching in the nsIWebBrowserFind impl.

Comment 6

[Akkana Peck]

I have an RFE for that, bug 14871.  So far it hasn't been considered very high
priority, so I haven't looked at it.

Comment 7

[amutch]

If this isn't going to be implemented soon or should be folder over into 14871,
please let us know so that we can modify the dialog appropriately on our end
(K-Meleon). The dialog in embedded examples should be modified as well but I'm
more concerned with the timeline on the functionality versus the dialog display.

Comment 8

[Akkana Peck]

If you look at bug 14871, it's marked Future, and no one has suggested so far
that it should be anything else.  If you disagree with that, you should make a
case for it in that bug.

Comment 9

[amutch]

I don't think there has been a big clamor for this but I just wanted to make
sure I knew where this was going. Thanks for the clarification. I'll file a
separate bug for the dialog box. This could be duped on 14871 or otherwise
closed out. If the functionality is implemented down the road, it should apply
equally to all apps. 

Comment 10

[Michael Lefevre]

duping per reporter's last comment



*** This bug has been marked as a duplicate of 14871 ***