Closed
Bug 3752
Opened 26 years ago
Closed 25 years ago
NS_MOUSE_LEFT_CLICK doesn't work
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P3)
Tracking
()
VERIFIED
FIXED
M7
People
(Reporter: mikepinkerton, Assigned: joki)
Details
(Whiteboard: 6/18 awaiting response from reporter)
I don't ever get NS_MOUSE_LEFT_CLICK events. I only seem to get
NS_MOUSE_LEFT_BUTTON_UP events instead.
Not sure if this is mac-only, but i suspect not.
Assignee | ||
Comment 1•26 years ago
|
||
NS_MOUSE_LEFT_CLICK events are generated for the content internally, not the
OS. I need more clarification on where and why you're looking for these to do
anything with this?
Reporter | ||
Comment 2•26 years ago
|
||
I'd rather check for a click than a button up to see if there is a mouse click.
If that's not the way it should be, though, then i'll deal. Just wondering why
there was a high level event if no one was supposed to look for it.
Assignee | ||
Comment 3•26 years ago
|
||
You can just for a click. I guess my point was that we generate these
internally based on our own restriction. ie. a mousedown and up on the same
content object is a click. A mousedown then up elsewhere is not. So where is
it that you don't get these? I can't really fix this without more specific
info.
Reporter | ||
Comment 4•26 years ago
|
||
In the toolbox frame event handling code, i don't get "clicks" only downs and ups
(nsToolboxFrame).
Assignee | ||
Updated•26 years ago
|
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 5•26 years ago
|
||
Well its pretty much fixed but let me explain the problem. We dispatch events
based on content, not frames. So in fact we are dispatching the click, we're
just sending it to the content. I've added it so that we also dispatch the
event to the frame we got the mouseup over but keep in mind this is less
reliable. If there are multiple frames associated with a piece of content only
one of them will get the click. But this should serve your purpose for the
moment anywyay.
Reporter | ||
Comment 6•25 years ago
|
||
joki, please smack me if i'm being lame, but it still doesn't work quite right so
i'm reopening the bug. When I get the NS_MOUSE_LEFT_CLICK event, the mouse
location (aEvent->point) is garbage (at least the y value us) so it's pretty much
useless.
Everything is ok if I continue to use NS_MOUSE_LEFT_BUTTON_UP.
Status: RESOLVED → REOPENED
Reporter | ||
Updated•25 years ago
|
Resolution: FIXED → ---
Reporter | ||
Comment 7•25 years ago
|
||
clearing resolution
Assignee | ||
Updated•25 years ago
|
Status: REOPENED → RESOLVED
Closed: 26 years ago → 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 8•25 years ago
|
||
Hey, I fixed a bug with click event coords the other day that should have fixed
this too.
Reporter | ||
Comment 9•25 years ago
|
||
how about letting me try it before you mark it fixed ;)
Assignee | ||
Comment 10•25 years ago
|
||
Nope. No chance. Its fixed. They're all fixed. Muhahahahaha
Updated•25 years ago
|
Whiteboard: 6/18 awaiting response from reporter
Comment 11•25 years ago
|
||
pinkerton, to verify or not to verify? Is it fixed?
Reporter | ||
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 12•25 years ago
|
||
marking verified.
Updated•6 years ago
|
Component: Event Handling → User events and focus handling
You need to log in
before you can comment on or make changes to this bug.
Description
•