Closed
Bug 59459
Opened 24 years ago
Closed 24 years ago
Problem with Select Area & Mouse Navigation
Categories
(Core :: Layout: Form Controls, defect, P3)
Tracking
()
People
(Reporter: brian, Assigned: rods)
References
Details
Build ID: 20001107 I'm not sure which component would handle this bug so I'm just putting it in the general category. If you click on a select area that is only one line (ex: the OS field on this bug report form), hold it (don't ever let up), and try to scrool up or down by moving above or beneath the dropdown list, it will NOT scroll through the list of options. If you click on a select area, expand it, let up on the mouse and click again and then try to scroll, it works fine. I'd appreciate this minor nusiance fixed. Thanks!
Comment 1•24 years ago
|
||
I see this on linux trunk build 2000110708. -> HTML Form Controls, OS -> ALL
Assignee: asa → rods
Component: Browser-General → HTML Form Controls
OS: Windows 98 → All
QA Contact: doronr → bsharma
Assignee | ||
Comment 3•24 years ago
|
||
This is a dup, I assume the reporter wants auto-scroll to work when the mouse is above or below the dropdown of a select control when the mouse button is held down
Status: NEW → ASSIGNED
Summary: Problem with Select Area & Mouse Navigation → [DUP]Problem with Select Area & Mouse Navigation
This is still an issue in 2001011920. Nominating Mozilla0.9 since never marked dupe. This behavior exists in Netscape 4.x and IE.
Keywords: mozilla0.9
Comment 7•24 years ago
|
||
> This is a dup, I assume the reporter wants auto-scroll to work when the mouse
> is above or below the dropdown of a select control when the mouse button is
> held down
That isn't the issue. The problem is that you can't scroll dropdowns using the
same mousedown that you used to open them.
Summary: [DUP]Problem with Select Area & Mouse Navigation → Problem with Select Area & Mouse Navigation
Assignee | ||
Comment 8•24 years ago
|
||
This is a dup and not a mozilla 0.9 issue *** This bug has been marked as a duplicate of 27315 ***
You need to log in
before you can comment on or make changes to this bug.
Description
•