66364 - cannot type in address bar if drop-down list with 2+ options appears and is ignored

Status: VERIFIED FIXED

(SeaMonkey :: Location Bar, defect)

Description

[Cormac F]

Okay, steps to reproduce:

1) Got a site and visit a number of pages e.g. go to www.ireland.com followed 
by www.ireland.com/services/email

2) Go to any other site

3) Click in the address bar, delete whats there, and begin to type in the 
original site name e.g. www.ireland.com

4) The drop down list will appear and the rest of the address will highlight. 
Ignore this and continue typing

5)When you finish typing the address, the cursor will jump forward a little and 
the first item in the drop-down list will remain highlighted.

6) Press and hold the delete key. You can't delete the text

You have to highlight it with  your mouse pointer to delete.
Admittedly, a minor enough bug, but they all count.
Using build 200101304 on WinNT4

Comment 1

[Warner Young]

I've seen this, too, but it doesn't always happen.  It seems like sometimes,
after the dropdown list appears, I *can* use delete or type more characters in
the URL bar.

Comment 2

[Asa Dotzler [:asa]]

->Editor

Comment 3

[rubydoo123]

sounds liek this is a xp apps bug, assigning to vishy

Comment 4

[Cormac F]

changed the summary. You can't type anything if you follow the steps outlined 
below. Which amkes this a bit more important. 
Feel free to change the summary if I havn't simplified it down enough.

Comment 5

[Chris McAfee]

over to alecf, history/urlbar

Comment 6

[Alec Flett]

this is a autocomplete bug, reassign to ducarroz (I don't know who owns this),
keeping myself on the cc

Comment 7

[Cormac F]

I imagine this bug is redundant, with the new autocomplete now working(mostly)?

Comment 8

[Jean-Francois Ducarroz]

reassign to hewitt

Comment 9

[Joe Hewitt (gone)]

Can't replicate this with the new widget

Comment 10

[sairuh (rarely reading bugmail)]

mass-verifying claudius' Fixed bugs which haven't changed since 2001.12.31.

if you think this particular bug is not fixed, please make sure of the following
before reopening:

a. retest with a *recent* trunk build.
b. query bugzilla to see if there's an existing, open bug (new, reopened,
assigned) that covers your issue.
c. if this does need to be reopened, make sure there are specific steps to
reproduce (unless already provided and up-to-date).

thanks!

[set your search string in mail to "AmbassadorKoshNaranek" to filter out these
messages.]