Closed
Bug 3272
Opened 26 years ago
Closed 26 years ago
problems w/ event object properties
Categories
(Core :: DOM: UI Events & Focus Handling, defect, P2)
Tracking
()
VERIFIED
FIXED
M7
People
(Reporter: sappling, Assigned: joki)
References
()
Details
1) References to event.screenX (and some others) cause the event handler to
terminate prematurely.
2) Event.type includes "on" at the start. I don't think it should (at least
that's not the behavior in IE4, Nav4, or IE5beta)
See example at URL specified above.
|
Assignee | |
Updated•26 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M6
|
|
Assignee | |
Comment 1•26 years ago
|
||
The 'on' before all the names part of this is fixed. The other event object
properties are still returning errors because they're not implemented yet.
|
|
Assignee | |
Updated•26 years ago
|
Target Milestone: M6 → M7
|
|
Assignee | |
Comment 3•26 years ago
|
||
This fix require work by both hyatt and me. Doesn't look like we'll get to it
this week so I'm moving it out to M7.
|
|
Assignee | |
Updated•26 years ago
|
Target Milestone: M7 → M8
|
|
Assignee | |
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
|
|
Assignee | |
Comment 4•26 years ago
|
||
event coords props are fixed now.
|
||
Updated•26 years ago
|
Status: RESOLVED → VERIFIED
|
|
||
Comment 5•26 years ago
|
||
Attempt to reference screenX does not seems to kill the event handler function.
At the start "A B onclick" is not written to the status line.
So working fine now. Marking as 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
•