Side navigation
#888 closed enhancement (wontfix)
Opened January 27, 2007 07:41PM UTC
Closed July 15, 2007 03:03PM UTC
Pass the current element to the event fixer
| Reported by: | yehuda | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | 1.1.4 |
| Component: | event | Version: | 1.1.3 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
The W3C spec has a currentTarget property on "e" that is effectively the same as the "this" variable inside jQuery event handlers. All browsers support it, except IE.
The event fixer creates the currentTarget property if it doesn't exist, but it currently overrides the handler to pass "this" in as a second param. It would be nice if jQuery did that by default (for a cost of 5 bytes)
Attachments (0)
Change History (2)
Changed April 27, 2007 03:08AM UTC by comment:1
| need: | → Review |
|---|
Changed July 15, 2007 03:03PM UTC by comment:2
| description: | The W3C spec has a currentTarget property on "e" that is effectively the same as the "this" variable inside jQuery event handlers. All browsers support it, except IE.\ \ The event fixer creates the currentTarget property if it doesn't exist, but it currently overrides the handler to pass "this" in as a second param. It would be nice if jQuery did that by default (for a cost of 5 bytes) → The W3C spec has a currentTarget property on "e" that is effectively the same as the "this" variable inside jQuery event handlers. All browsers support it, except IE. \ \ The event fixer creates the currentTarget property if it doesn't exist, but it currently overrides the handler to pass "this" in as a second param. It would be nice if jQuery did that by default (for a cost of 5 bytes) |
|---|---|
| milestone: | → 1.1.4 |
| resolution: | → wontfix |
| status: | new → closed |
| version: | → 1.1.3 |
I agree with Brandon - the current solution is feasible.
But since jQuery already passes the context properly is currentTarget really needed?