Closed
Bug 35606
Opened 25 years ago
Closed 25 years ago
incorrect usage of mouseup on xul widgets
Categories
(SeaMonkey :: General, defect, P3)
SeaMonkey
General
Tracking
(Not tracked)
VERIFIED
FIXED
M18
People
(Reporter: Brade, Assigned: bugs)
References
Details
(Whiteboard: [nsbeta2+])
I was talking with joki about event handling and he reminded me that clicking on
controls and links should actually trigger on mouseclick rather than mouseup. I
happened to later notice that in xulBindings.xml there is code like this:
<handler type="mouseup" value="this.checked = !this.checked;" />
joki confirmed that this is a bug (as written above).
Updated•25 years ago
|
Target Milestone: --- → M17
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M17 → M16
Hmmm, this might be bad. Real bad. We should fix this for beta 2.
Keywords: nsbeta2
Target Milestone: M16 → M18
Comment 5•25 years ago
|
||
A standard use case is for a user to mousedown on a checkbox or radio, change
their mind, drag away from the control and mouseup -- result is no change to
the state of the control.
The problem is that when they mouseup "just somewhere else" and that is over
a checkbox/radio or its label, they have now changed this other control's state
-- likely _without_realizing_ that they have done so (try it out in some of
the mail pref dialogs).
That's not good (especially as this contradicts a standard UI behaviour).
Whiteboard: [need info]
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 7•25 years ago
|
||
fixed
Comment 8•25 years ago
|
||
wfm on 60608 win98, win2k and linux. waiting for mac verification...
Comment 10•25 years ago
|
||
*** Bug 43760 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•