271102 - FastFind behavior changed for non-matching strings since Find Toolbar was implemented

Status: RESOLVED INVALID

(Toolkit :: Find Toolbar, defect)

Description

[Norbert]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

In Firefox <1.0 there was some kind of auto correction implemented in FastFind:

If a website for example contains "Firefox" and I accidentally enter a wrong
additional letter, for example the word "firefiox", Firefox <1.0 finds the word
"Firefox".

Has this feature been removed intentionally?

Reproducible: Always
Steps to Reproduce:

Comment 1

[Nickolay_Ponomarev]

there has never been any autocorrection in fayt. It could find "Firefox",
because no other words began with "Firef".

Comment 2

[Norbert]

(In reply to comment #0)

Sorry, but this is incorrect. Please test it with a old 0.8 or 0.9 version!

Comment 3

[Mike Connor [:mconnor]]

There has never been any auto-correct feature along these lines.  This would
require a lot of code to guess at "close" words that just doesn't exist.

As comment 1 says, it would have found firefox from the firef fragment, the only
different in the Find Toolbar (implemented AFTER 0.9) will deselect the match
found if you keep typing, which is correct behaviour.  "Firefi" should never
match firefox.

This is by design, INVALID.  We won't change this, its just wrong behaviour.

Comment 4

[Norbert]

(In reply to comment #3)

You have misunderstood me!

I mean that old Firefox has a simple autocorrect that recognizes for example a
letter to mutch in the search string!

In 0.8 (or 0.9) entering the letters 
f i r e f g

correctly does not highlight anything.

If I add now
o
to the search string, old firefox recognizes that only the g was incorrect and
highlights "firefo" of the word "firefox".

I'm absolutely sure of this behaviour!!! Please test it!

Comment 5

[Norbert]

(In reply to comment #3)
"Firefi" should never
> match firefox.

Here I see that you have misunderstood me. "Firefi" DOES NOT and should not
match "Firefox", I agree.

But if you now add a "o" to "firefi"-string, old firefox-browser auto-correct
the search-string to "firefo". And this DOES match!

Please Note: I mean FastFind, not a "normal" search!

Comment 6

[Nickolay_Ponomarev]

That's not autocorrection at all. Comments 5 and 6 correctly describe the bug,
which I see. Not sure if that change was intentional, but reopening, since it's
not what me and mconnor thought you meant.

Comment 7

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 8

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 9

[Norbert]

I think current behaviour is better solution than the old one. Closing.