Closed
Bug 40127
Opened 25 years ago
Closed 25 years ago
moz can't handle pull down menus
Categories
(Core :: Layout: Form Controls, defect, P3)
Tracking
()
CLOSED
WORKSFORME
People
(Reporter: vanbalen, Assigned: rods)
References
()
Details
This seems to be related to handling .asp pages so I put it under
Browser-General for lack of a better category...
I'm using today's build (May 22, 2000) under Linux Mandrake 7.0-2 and Gnome.
The problem on this page (carpoint.msn.com) appears to be that when you try to
choose a "make" under the "make..." menu can result in a random selection (I.e.
choosing "Volkswagen can result in choosing "Aston Martin" instead and so on).
Also observed crashes (browser stoped responding and I ended up kill -9ing it)
whenever I proceeded to choose a model and click on the "Go" button to view its
page.
Comment 1•25 years ago
|
||
Confirmed on Linux Build 2000052109. Please add crash keyword and raise
severity to critical.
Comment 2•25 years ago
|
||
the crash thing is prob a JS problem and is unrelated, please split that off as
a separate bug.
I encounter no problems with the make <SELECT>, but reassigning to rods for eval
Assignee: asadotzler → rods
Component: Browser-General → HTML Form Controls
QA Contact: jelwell → ckritzer
New bug 40172 created with JS crash.
Update on <select> prob: I've messed with it a little more and I think it only
happens when there's no mouse-up event between scrolling and selecting (similar
to what I got used to doing with Netscape's pulldown menus). Don't know if you'd
consider this a bug or not.
| Assignee | ||
Comment 5•25 years ago
|
||
Ok, there is no crash for the combo, but what is the issue with this bug now?
Comment 6•25 years ago
|
||
WORKSFORME on build 2000060508 Linux.
The crash bug is certainly there, but the <select> part of this bug has been
resolved.
Reporter: please reopen this bug if you can reproduce in a new build.
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
Works right with 2000060508/Linux. Closing
Status: RESOLVED → CLOSED
You need to log in
before you can comment on or make changes to this bug.
Description
•