Closed
Bug 91338
Opened 24 years ago
Closed 5 years ago
[meta] double-click detection
Categories
(Core :: DOM: UI Events & Focus Handling, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jruderman, Unassigned)
References
(Depends on 2 open bugs)
Details
(Keywords: meta)
bug 39192 Drag+click interpreted as double-click (fixed on Win32 only)
bug 53144 Click, then drag interpreted as double-click (invalid)
bug 53485 Mozilla too lenient on double-click detection? (timing) (fixed)
bug 89923 click to cancel menu counts toward double click
bug 91337 double-click is detected even if two clicks were on different objects
Reporter | ||
Updated•24 years ago
|
Reporter | ||
Updated•24 years ago
|
based on the number of bugs still open here, as well the number of duplicates in
each of these bugs, this ought to be assigned a higher priority/severity/target
milestone. severity normal is suggested, at the very least, as it is the
predominant severity for the depending bugs.
it would appear that the remaining open bugs appear to be tightly related, and
thus the collective size of this problem warrants a target milestone of either
1.01 or 1.0, and possibly even nsmeowfood.
Updated•23 years ago
|
QA Contact: madhur → rakeshmishra
Comment 2•23 years ago
|
||
Bug 142800 I just created concerns the HTML composer for web pages or mail/news
(I only tested on Win98/2k) having the currently selected item behave as if it
was double-clicked, if there is a double-click in the scroll bar arrows, or the
scroll bar space - but not on the scroll bar sliders themselves. The affected
types of items are those which have properties boxes, such as tables, images,
targets, links and horizontal rules. This bug does not cause the effective
double-clicking of ordinary text.
Updated•22 years ago
|
QA Contact: rakeshmishra → trix
Assignee | ||
Updated•6 years ago
|
Component: Event Handling → User events and focus handling
Comment 4•5 years ago
|
||
No activity for 14 years, closing
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•