#7628 closed bug (fixed)
Incorrect documentation for event.currentTarget
| Reported by: | masklinn | Owned by: | ajpiano |
|---|---|---|---|
| Priority: | low | Milestone: | 1.5 |
| Component: | support | Version: | 1.4.4 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
The documentation for event.currentTarget states:
This property will always be equal to the this of the function.
but it is not the case if jQuery.proxy (or some other form of context-binding) was used. In this case, this will be the bound context while currentTarget will be the element the event was bound on (or for in the case of .live and .delegate).
Change History (3)
comment:1 Changed 6 years ago by ajpiano
- Component changed from unfiled to support
- Keywords needsdoc added
- Owner set to ajpiano
- Priority changed from undecided to low
- Status changed from new to assigned
comment:2 Changed 6 years ago by ajpiano
- Resolution set to fixed
- Status changed from assigned to closed
comment:3 Changed 6 years ago by jitter
- Keywords needsdoc removed
Note: See
TracTickets for help on using
tickets.
http://api.jquery.com/event.currentTarget/ i added a note about this and revised the language. even though it's not a particularly high priority issue, as i think people who are using $.proxy aren't trying to use event.currentTarget as a "shortcut" to this because of this docs error. you never can be too careful though, i guess.