Closed Bug 90123 Opened 24 years ago Closed 24 years ago

autocomplete drop-down shows up elsewhere on window

Categories

(SeaMonkey :: Location Bar, defect)

x86
Linux
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 86256

People

(Reporter: joseph, Assigned: alecf)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.2) Gecko/20010702 BuildID: 2001070209 Under Gnome/Enlightenment on RH 6.2, the autocomplete drop-down shows up where the browser window was originally opened, even after the window is moved. The popup with the "v" shows up in the right place, but if I clear the URL input and start typing, the drop-down (with "search Google" etc. in it) shows up at some other spot on the screen. Reproducible: Always Steps to Reproduce: 1.Create new window. 2.Move it. 3.Type in URL input area. Actual Results: Drop-down shows up somewhere other than below URL input area. Expected Results: Drop-down should appear directly below URL input area.
wfm 2001070921 linux gnome/sawfish
ccing hewitt and blizzard
This might be a dupe of bug 86256. In that bug it only happens when the url is not in the autocomplete list, when just the search field pops up. Reporter - is that what happens to you or is this a different issue?
I have autocomplete turned off. So, for example, if I start typing http://slashdot.org, what I see is a little window placed "wherever" that says "Search Google for h" -> "Search Google for ht" ... etc. The misplaced window also has roughly two lines of blank white space above the gray part with the "Search Google ..." in it. I never use autocomplete in any browser that lets me turn it off and can't comment on how that might affect what I'm seeing.
Marking as dupe of 86256 as this also happens without anything in the autocomplete list. *** This bug has been marked as a duplicate of 86256 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
verified dup
Status: RESOLVED → VERIFIED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.