Closed
Bug 40003
Opened 26 years ago
Closed 26 years ago
mousedown on dropdown listbox, mouseup elsewhere triggers onclick
Categories
(Core :: DOM: Core & HTML, defect, P3)
Tracking
()
People
(Reporter: jruderman, Assigned: rods)
References
()
Details
(Keywords: testcase)
Attachments
(1 file)
|
195 bytes,
text/html
|
Details |
1. load attachment to bug 39985
2. mousedown on the dropdown listbox in the light gray area
3. mouseup somewhere else on the page
result: onmousedown, onmouseup, onclick
expected: same as above, but onclick shouldn't trigger
| Assignee | ||
Comment 2•26 years ago
|
||
Please provide a simple testcase for onclick and onselect, I am seeing the
problem.
Status: NEW → ASSIGNED
| Reporter | ||
Comment 3•26 years ago
|
||
| Assignee | ||
Comment 5•26 years ago
|
||
This is related to to, but a different bug than 40382.
On PreHandleEvent SetClickCount is called which makes sure the down and up
content pointers match and clear the click count if they do not (the cause of
bug 40382).
The problem with this bug is the PreHandleEvent correctly "kills" the dispatch
of the click event (by setting the clickcount to 0, but the PostHandleEvent does
not call SetClickCount so the event always gets dispatched.
| Assignee | ||
Comment 6•26 years ago
|
||
Adding a call to SetClickCount on line 835 seems to fix this problem, but I am
not sure what else it or may not break.
SetClickCount(aPresContext, (nsMouseEvent*)aEvent, aStatus);
| Assignee | ||
Comment 7•26 years ago
|
||
reassigning to joki cc'ing pollmann,saari
This is probably nsbeta2 or FCS
| Assignee | ||
Comment 10•26 years ago
|
||
This is the same issue as 40382. It knowing how to enable and disable the
sending of the onclick depending on whether the mouse is released on or off the
select.
*** This bug has been marked as a duplicate of 40382 ***
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•