Closed
Bug 74468
Opened 23 years ago
Closed 23 years ago
MouseEvent.getButton() doesn't return -1 on mouse over if no button is pressed
Categories
(Core :: DOM: Events, defect)
Core
DOM: Events
Tracking
()
VERIFIED
WONTFIX
People
(Reporter: edburns, Assigned: edburns)
References
()
Details
Attachments
(2 files)
425 bytes,
patch
|
Details | Diff | Splinter Review | |
435 bytes,
patch
|
Details | Diff | Splinter Review |
MouseEvent.getButton() doesn't return -1 on mouse over if no button is pressed
Comment 5•23 years ago
|
||
r=blake if joki and jst are okay with this.
Comment 6•23 years ago
|
||
MouseEvent.button is an unsigned property, i.e. it can't be negative so we can't return -1, still investigating...
Comment 7•23 years ago
|
||
Isn't the real solution to the problem here to check if event.detail == 0 when the mouse over event fires, if event.detail is 0 then no button is clicked, or am I reading the spec wrong?
Comment 8•23 years ago
|
||
I said the same thing. The second patch supposedly addresses that problem by casting it to a PRUint16. That was timeless' suggestion, and he says it'll work propertly...(if this isn't right, there's pre-existing code in the function that does this that needs changing) But I think Johnny is right about event.detail (per the spec and our implementation), making this a wontfix...
Thanks, that works for me. Marking should I mark invalid? Reassign?
Comment 10•23 years ago
|
||
WONTFIX sounds good...
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•