406934 - [FAYT] Apostrophe (') or slash (/) restarts find as you type (type ahead) search.

Status: RESOLVED INCOMPLETE

(Camino Graveyard :: General, defect)

Description

[Ilya Sherman]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en; rv:1.8.1.11) Gecko/20071128 Camino/1.5.4
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en; rv:1.8.1.11) Gecko/20071128 Camino/1.5.4

Find as you type cannot be used to search for text containing apostrophes or slashes, as the search is restarted.  For example, searching for "html/css" results in a search for "html" which is overridden by a search for "css".

Reproducible: Always

Steps to Reproduce:
1. Invoke fayt to search for a string containing a slash or apostrophe (e.g. "Tim's bakery")
2.
3.
Actual Results:  
Find as you type resets search text on every slash or apostrophe (and for apostrophes switches to link mode).  Hence, the above search for "Tim's bakery" will instead search links for "s bakery".

Expected Results:  
The page should be searched for the full string entered before the fayt times out, so in the above case, "Tim's bakery".

Comment 1

[Jean-Michel Reghem]

Works in Firefox 3.0b1.
This seems a dupe of bug 311376 or an other listed in meta bug 320465

Comment 2

[Ilya Sherman]

(In reply to comment #1)
> Works in Firefox 3.0b1.
This works in Firefox because Firefox's search is customized, and does not rely on the core FAYT.

> This seems a dupe of bug 311376 or an other listed in meta bug 320465
If you read carefully, you'll notice that those bugs relate to FAYT interaction with textareas, whereas this is just purely related to FAYT functionality.

Comment 3

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

This actually works in SeaMonkey (which is the other consumer of the core FAYT), so the bug must sit somewhere between us and FAYT.  I wonder if it's related to whatever breaks bug 244175?

Comment 4

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

(In reply to comment #3)
> This actually works in SeaMonkey (which is the other consumer of the core
> FAYT), so the bug must sit somewhere between us and FAYT.  I wonder if it's
> related to whatever breaks bug 244175?

Heh. :P Mark had discovered this in Feb 2006:

(bug 244175 comment #32)
> I also noticed that in Camino, we can't use TAF to search for a string that
> contains a forward slash or single quote.  Those characters restart TAF. 
> They're searchable in SeaMonkey.