#527 closed enhancement (fixed)
Requesting dojo.event.connect set up currentTarget in IE
Reported by: | Owned by: | sjmiles | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Core | Version: | 0.2 |
Keywords: | event, connect, currentTarget | Cc: | [email protected]… |
Blocked By: | Blocking: |
Description
Dojo "fixes" various event properties, giving standard properties their standard values in IE. Apparently currentTarget is not currently set up, and it would be very nice if it were.
Change History (7)
comment:1 Changed 16 years ago by
comment:2 Changed 16 years ago by
Milestone: | → 0.3release |
---|---|
Owner: | changed from anonymous to sjmiles |
comment:3 Changed 16 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:5 Changed 16 years ago by
Keywords: | event connect currentTarget added |
---|
comment:6 Changed 16 years ago by
(In [3309] sjmiles) "Added (optional) second parameter (sender) to event.browser.fixEvent to fix missing currentTarget property on IE. Modified five instances of fixEvent invocations to pass 'this' for 'sender'."
Thanks!
Note: See
TracTickets for help on using
tickets.
I guess I should thank [email protected]… for creating a ticket for me. For a detailed explanation of the problem, please look at my original message on dojo-interest.
The crux of the matter is that while IE events don't supply the currentTarget property, you can work around that by referencing this, which is effectively the same as the currentTarget would be:
But dojo doesn't capture it in this or in currentTarget.
The problem would be solved if dojo would, for IE, save the original
this
into the fixed-up event ascurrentTarget
.References
The best explanation comes from http://www.quirksmode.org/js/events_order.html