342633 - Single Char in adress bar may return list of unrelated history items.

Status: VERIFIED WORKSFORME

(Camino Graveyard :: Location Bar & Autocomplete, defect)

Description

[Philipp Kruse]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.0.4) Gecko/20060613 Camino/1.0.2 (MultiLang)
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.0.4) Gecko/20060613 Camino/1.0.2 (MultiLang)

When entering a single char in the adress bar there seems to be a problem when fetching the list of appropriate history items. More specifically, it just returns the list corresponding to the string entered before. This only seems to occur with single chars and fixes itself when hitting another key. Switching Tabs resets this.

Reproducible: Always

Steps to Reproduce:
1. Enter some characters (one or more) in the adress bar.
2. Clear the adress bar.
3. Enter a single character.

Actual Results:  
The auto-complete list will not match the character that was entered.

Expected Results:  
Obviously, this should return a list of matching sites from the history.

Comment 1

[Peter Jaros (:peeja)]

WFM on recent nightly build and 1.0.2.  I type "bug" (bugzilla urls come up), press option-delete (bar clears and urls go away), then type "g".  Google and gmail urls pop up.

Perhaps try a clean profile (after populating it with some history items).  If that does it, it's a corrupted history file.

Comment 2

[Chris Lawson (gone)]

I can't repro either, using 1.0.2 at the moment. I agree that this is probably a busted history.dat file in the profile.

cl

Comment 3

[Peter Jaros (:peeja)]

(In reply to comment #2)
> I can't repro either, using 1.0.2 at the moment. I agree that this is probably
> a busted history.dat file in the profile.

Philipp, could you attach your history.dat file to the bug?

Comment 4

[Philipp Kruse]

Attachment: My history.dat

Comment 5

[Peter Jaros (:peeja)]

I can't repro on either build using the attached history.dat and the steps I used before.

Philipp, can you try the exact steps I used in comment 1 and see if that makes it happen on your machine?

Comment 6

[Philipp Kruse]

Clearing the history seems to have solved it.