Closed Bug 35606 Opened 25 years ago Closed 25 years ago

incorrect usage of mouseup on xul widgets

Categories

(SeaMonkey :: General, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

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).
Target Milestone: --- → M17
Status: NEW → ASSIGNED
Target Milestone: M17 → M16
*** Bug 37151 has been marked as a duplicate of this bug. ***
*** Bug 40553 has been marked as a duplicate of this bug. ***
Hmmm, this might be bad. Real bad. We should fix this for beta 2.
Keywords: nsbeta2
Target Milestone: M16 → M18
[need info] What will the user see that is bad?
Whiteboard: [need info]
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]
Putting on [nsbeta2+] radar for beta2 fix.
Whiteboard: [nsbeta2+]
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
wfm on 60608 win98, win2k and linux. waiting for mac verification...
verified on mac. Thanks Blake.
Status: RESOLVED → VERIFIED
*** Bug 43760 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.