315599 - Clicking autocomplete entry without moving mouse doesn't work

Status: RESOLVED DUPLICATE of bug 306538

(Firefox :: Address Bar, defect)

Description

[Ron Baldwin]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051025 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051025 Firefox/1.5

Clicking on an autocomplete entry with the mouse usually (but not always) closes the dropdown without populating the textbox.  Using the keyboard (Enter) seems to always work.

Reproducible: Sometimes

Steps to Reproduce:
1. Trigger autocomplete either by typing or clicking in an empty textbox.
2. Click on an entry in the dropdown.


Actual Results:  
The dropdown goes away, and the textbox is (usually) not populated.

Expected Results:  
Textbox is populated with the autocomplete entry clicked on.

Comment 1

[Ron Baldwin]

BTW, this is a regression from 1.0.x.  I assume that 1.8rc2 is the right flag for the Fx 1.5 branch?

Comment 2

[Jesse Ruderman]

WFM Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8) Gecko/20051107 Firefox/1.5

Comment 3

[Adam Guthrie]

Ron, can you reproduce this in a clean profile? 

Comment 4

[Scott MacGregor]

WFM on the latest RC 2 candidate build:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051107 Firefox/1.5

minusing as a stop ship bug for 1.5. Maybe some other folks will come up with steps to reproduce.

Comment 5

[Ria Klaassen (not reading all bugmail)]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051108 Firefox/1.5 ID:2005110803

I see this too sometimes, when I don't click exactly in the center of the username; mostly when I'm in a hurry. Although the entry is highlighted, I don't seem to touch it on a sensitive spot. 

Comment 6

[Ria Klaassen (not reading all bugmail)]

Attachment: screenshot

This click will result in an empty inputfield.

Comment 7

[Ron Baldwin]

Ok, clown nose for me.  The bug as reported is invalid, but after more testing I did find a case where it can be reproduced.

My original testing was done after turning off any extensions I thought might have anything to do with textboxes.  After testing on a new profile as requested by Adam and finding that it worked correctly, I started adding my extensions to the new profile to see if one of them was causing the problem.  Would you believe that TickerFox (puts a live Fx download count in the status bar) was causing the problem?  Weird.

Anyway, here are the new steps:
1. Set focus to a textbox that has autocomplete entries.
2. Position the mouse such that it will be over an entry from the dropdown when it appears.
3. Enter a character that will cause autocomplete to show. *Do not move the mouse*.
4. Click without moving the mouse.  Since the entries highlight on mouse move, no entry will be selected.  Clicking will dismiss the dropdown without populating the textbox.

These steps may seem somewhat contrived, but it happens (at least to me) more often than one might think.  Imagine you're using a well known form (e.g. a Bugzilla bug entry) and doing something you do all the time (e.g. add yourself to the CC list).  You click in the field, move the mouse to where you know the entry you want will be, hit the first letter of the entry and then click.  If you didn't happen to move the mouse after hitting the first letter, the textbox doesn't get filled in.

Comment 8

[Ria Klaassen (not reading all bugmail)]

Hm, it doesn't bother me, but I tested it on a new profile, like always. :)

Comment 9

[Ron Baldwin]

(In reply to comment #8)
> Hm, it doesn't bother me, but I tested it on a new profile, like always. :)
> 

Doesn't bother you (i.e. it doesn't affect your normal usage), or you can't reproduce?

Also, the issue in the screenshot looks like a different (but related) problem.  If you click on the dropdown window outside the area that gets highlighted, the dropdown stays up and nothing happens.  If you click on what looks like the first pixel of the highlight around the dropdown borders (like in the screenshot), the dropdown will go away and nothing gets entered in the textbox.

This probably needs to be entered as a separate bug report.

Comment 10

[Adam Guthrie]

Problems caused by extensions aren't addressed on bugzilla.mozilla.org. You should consult the owner of the extension about fixing this bug.

Comment 11

[Ron Baldwin]

(In reply to comment #10)
> Problems caused by extensions aren't addressed on bugzilla.mozilla.org. You
> should consult the owner of the extension about fixing this bug.
> 

You're a bit too trigger happy on the INVALID there.  If you read my entire comment 7, you'll see there are new steps that are 100% reproducible.  Not to mention the additional bug referred to in comment 6 and comment 9.

Comment 12

[Adam Guthrie]

Neither one of the new issues that you've morphed this bug into regressed from 1.0 (or possibly ever), so that takes out the chance of them stopping a release. Not to mention that both of these bugs are pretty minor, and probably dupes.

Comment 13

[Martijn Wargers (dead)]

The issue mentioned in comment 7 should be fixed by bug 306538. It is fixed on trunk, not on branch. That means that Firefox1.7RC1 doesn't have it fixed.

Comment 14

[Ria Klaassen (not reading all bugmail)]

(In reply to comment #9)
It doesn't bother me, because I don't see it as a big problem.
The issue I mentioned in comment #5 seems to be resolved in trunk, I can't reproduce it there.

Comment 15

[Ron Baldwin]

(In reply to comment #12)
> Neither one of the new issues that you've morphed this bug into regressed from
> 1.0 (or possibly ever), so that takes out the chance of them stopping a
> release. 

Agreed.

> Not to mention that both of these bugs are ... probably dupes.

Don't know about the bug in comment 6 and comment 9, but Martijn is right--comment 7 (which is what this bug has become) is a dupe of bug 306538.


*** This bug has been marked as a duplicate of 306538 ***

Comment 16

[Ria Klaassen (not reading all bugmail)]

In "View Bug Activity" I can see that I set a request for blocking1.8rc2 but I did NOT do that. Don't know what was wrong with the server/software. 

Comment 17

[Ron Baldwin]

(In reply to comment #16)
> In "View Bug Activity" I can see that I set a request for blocking1.8rc2 but I
> did NOT do that. Don't know what was wrong with the server/software. 

If I had to guess, I'd say you had a mid-air collision with mscott when he minused the flag.  You then hit back, refreshed to get the new page, and resubmitted.  But since Fx remembers form values on a refresh (e.g. the '?' before it was minused), you ended up overwritting the flag when you added comment 5.