Clicking on <select> element when autocomplete list is open doesn't collapse the list

NEW
Unassigned

Status

()

Core
Widget: Gtk
14 years ago
11 years ago

People

(Reporter: Scott Gifford, Unassigned)

Tracking

({testcase})

Trunk
x86
Linux
testcase
Points:
---
Bug Flags:
blocking1.9 -
wanted1.9 +
blocking1.8.1.5 -

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

14 years ago
I'm seeing a page where typing in information that starts autocompletion in a
text input stops a select dropdown list from working when it's clicked on.  This
is on Firefox PR1:

  Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20040911 Firefox/0.10

Here's how I can reproduce it:

1. Visit http://www.smartpages.com
2. Enter Flint in the City text input, and hit Go
3. Hit back
4. Enter Ann Arbor in the City text input, and hit Go
5. Hit back
6. Start to type Flint in the City text input
7. When the list of possible autocompletions appears, try to click on the State
select dropdown

Actual Results: The select dropdown doesn't get focus, and nothing can be
selected, for at least the first few clicks.  Sometimes after 3 clicks it will
work OK; sometimes it will require more, and sometimes it apparently never
starts working.

Expected Results: A working select dropdown.

It works OK if you use the keyboard to navigate or if you cause the autocomplete
list to be dismissed.

Comment 1

14 years ago
Work for me with FF PR1 The state dropdown gets focus on the first click. The
autocomplete list vanishes when I select the state dropdown. No problem
selecting a state.
(Reporter)

Comment 2

14 years ago
James - What platform are you on?

Comment 3

14 years ago
This is a problem for me as well.  Using the 1.0 release of firefox (v0.10 i
guess).  I run into this problem all the time, and it's really annoying.  My
platform is OSX, so if James is also on OSX it's probably OSX not doing the
right thing.  Again.

Comment 4

13 years ago
*** Bug 301245 has been marked as a duplicate of this bug. ***

Comment 5

13 years ago
*** Bug 301245 has been marked as a duplicate of this bug. ***

Comment 6

13 years ago
I was seeing this bug in the 20050821 nightly as well. The autocomplete box
seems to steal mouse focus on the whole page until it's dismissed so that doing
anything else on the page takes 2 clicks instead of one. Maybe the select box
thing is a side effect of that?

Comment 7

13 years ago
This affects me too on X11 with Firefox 1.5 beta 1. When the autocomplete box is
visible it is impossible to get the select menu to drop down. If I click
elsewhere on the page to make the autocomplete box go away then I can use the
select menu as normal.

Comment 8

13 years ago
Exists on 1.5b2 on Mac as well.

Comment 9

13 years ago
*** Bug 314657 has been marked as a duplicate of this bug. ***

Comment 10

13 years ago
Confirming with Windows XP SP1 and FF 1.5 RC2&3, suggesting change to OS: ALL.

Comment 11

12 years ago
Confirming on Firefox 1.5.0.2 under Mac OS X 10.4.5 (PPC, if it makes a difference)

Comment 12

12 years ago
Confirmed with 1.5.0.4 under Linux, does not happen in Windows XP (1.0.7 and 1.5.0.4 tested)

Comment 13

12 years ago
Mass edit: Changing QA to default QA Contact
QA Contact: davidpjames → password.manager

Comment 14

12 years ago
Mass edit: Setting correct QA for location bar/autocomplete. My bad. I forgot I had once been Autocomplete QA too. Hmm, why can't I just set the QA of bugs to the default QA of the component in a mass edit rather than having to do it manually...?
QA Contact: password.manager → location.bar

Comment 15

12 years ago
This bug makes PHPMyAdmin /infuriating/ to use. 

Why is the status still NEW? It has been confirmed on Linux and OSX 
by multiple users, has several votes and several CC's. Surely it 
could at least be marked CONFIRMED. Better yet, FIXED! =D

Comment 16

12 years ago
Seems to be fixed with 2.0RC2 on Mac

Comment 17

12 years ago
Created attachment 241779 [details]
testcase

Updated

12 years ago
Assignee: bugs → nobody
Component: Location Bar and Autocomplete → Widget: Gtk
Product: Firefox → Core
QA Contact: location.bar → gtk
Summary: autocomplete list breaks mouse clicks on select dropdown → Clicking on <select> element when autocomplete list is open doesn't collapse the list
Version: 1.0 Branch → 1.8 Branch
broken with Firefox 1.5 and 2.0 on GNU/Linux

Reproducible with the bugzilla simple search.
Flags: blocking1.8.1.5?

Updated

11 years ago
Duplicate of this bug: 383646

Updated

11 years ago
Keywords: testcase
Version: 1.8 Branch → Trunk

Updated

11 years ago
Duplicate of this bug: 375025
Not blocking a security release, we've obviously been able to live with this problem for many releases. If you want it fixed a better bet it to get it fixed in a future release.
Flags: blocking1.8.1.5? → blocking1.8.1.5-
Flags: blocking1.9?

Updated

11 years ago
Duplicate of this bug: 317272

Updated

11 years ago
Duplicate of this bug: 314853

Comment 24

11 years ago
Still there (as described in bug 314853 (duped above)) with
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a6pre) Gecko/20070702 Minefield/3.0a6pre
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.5pre) Gecko/20070702 BonEcho/2.0.0.5pre
Flags: blocking1.9? → blocking1.9-
Whiteboard: [wanted-1.9]
Duplicate of this bug: 397449
For what it's worth this causes enough pain with bugzilla that I turned off form fill to keep my sanity.

Comment 27

11 years ago
See also bug 269034, a similar bug on Mac.
Since this is thed ONLY popup which behaves this way, I somehow doubt it's a pure widgetry issue, esp. given the Mac problem.  But whatever.
(In reply to comment #28)
> Since this is thed ONLY popup which behaves this way, I somehow doubt it's a
> pure widgetry issue, esp. given the Mac problem.  But whatever.
> 
Feel free to change the component as needed, you are probably one of those who got the power :)

From the presented choice it looks like event handling to me.
Well.  Both dbaron and I filed our bugs (which are definitely duplicates of each other, though I'm not convinced they're duplicates of this bug in spite of being marked so) in toolkit:autocomplete.  I still think that's the right place.  But I'm not getting into any sort of unduping war here.
(Reporter)

Comment 31

11 years ago
Boris -

Looking at the bug reports, I think you and dbaron are reporting the same thing as I reported in this bug, although both of you described it more clearly than I managed to.  I agree with you it's very frustrating, and would love for it to be fixed.  Please feel free to make whatever changes to the bug you think will help this happen, including changing the description to make it clearer, or moving it the bug another component.  After all, it certainly hasn't gotten much love in its current component.  :-)
Flags: wanted1.9+
Whiteboard: [wanted-1.9]
You need to log in before you can comment on or make changes to this bug.