Closed
Bug 10330
Opened 26 years ago
Closed 25 years ago
Event::currentNode always null
Categories
(Core :: DOM: Events, defect, P3)
Tracking
()
VERIFIED
FIXED
M16
People
(Reporter: dbaron, Assigned: joki)
References
()
Details
Attachments
(3 files)
It seems (at least for click events) that Event::currentNode always returns
null. See the above test (for now, I'll probably write a better one soon).
Judging from
http://lxr.mozilla.org/seamonkey/source/layout/events/src/nsDOMEvent.cpp#169 ,
this seems like a rather general problem.
|
Assignee | |
Updated•26 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M11
|
|
Assignee | |
Comment 1•26 years ago
|
||
Yup. Haven't gotten that one yet, still trying to figure out how I want to
implelement it.
|
|
Assignee | |
Updated•26 years ago
|
Target Milestone: M11 → M12
|
|
Assignee | |
Comment 2•26 years ago
|
||
Setting milestone to m12
|
|
Assignee | |
Updated•26 years ago
|
Target Milestone: M13 → M14
|
|
||
Updated•26 years ago
|
Target Milestone: M14 → M16
|
|
||
Comment 4•26 years ago
|
||
Moving M16.
|
|
Assignee | |
Comment 5•25 years ago
|
||
Fixed, though the name has changed. Current spec call it Event::currentTarget.
Attaching modified test case.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Comment 6•25 years ago
|
||
|
|
Assignee | |
Comment 7•25 years ago
|
||
|
|
Assignee | |
Comment 8•25 years ago
|
||
|
||
Updated•25 years ago
|
Component: DOM Level 2 → DOM Events
You need to log in
before you can comment on or make changes to this bug.
Description
•