Skip to main content

Bug Tracker

Side navigation

#9125 closed feature (wontfix)

Opened May 05, 2011 03:31PM UTC

Closed June 07, 2011 06:53PM UTC

Parse arguments to callbacks

Reported by: funcoder@live.com Owned by:
Priority: low Milestone: 1.7
Component: effects Version: 1.5
Keywords: needsreview,1.7-discuss Cc:
Blocked by: Blocking:
Description

Callback functions e.g. for "fadeIn" often point at functions in objects.

The problem is that "this" in that functions refere to the object which is manipulated in this case a html dom object.

This is why we need parameter support for these callbacks so we can pass for example the original object or an id or whatever we want.

Attachments (0)
Change History (10)

Changed May 06, 2011 07:04PM UTC by timmywil comment:1

component: unfiledeffects
keywords: → needsreview
priority: undecidedlow
status: newopen

Changed May 22, 2011 07:27PM UTC by john comment:2

keywords: needsreviewneedsreview,1.7-discuss

Nominating ticket for 1.7 discussion.

Changed May 22, 2011 09:06PM UTC by rwaldron comment:3

description: Callback functions e.g. for "fadeIn" often point at functions in objects. \ The problem is that "this" in that functions refere to the object which is manipulated in this case a html dom object. \ \ This is why we need parameter support for these callbacks so we can pass for example the original object or an id or whatever we want. \ \ Callback functions e.g. for "fadeIn" often point at functions in objects. \ The problem is that "this" in that functions refere to the object which is manipulated in this case a html dom object. \ \ This is why we need parameter support for these callbacks so we can pass for example the original object or an id or whatever we want.\ \

+0, Use. jQuery.proxy

Changed May 23, 2011 12:48AM UTC by jaubourg comment:4

-1, JS has closures, jQuery has proxy.

Changed May 23, 2011 04:45AM UTC by timmywil comment:5

-1, That doesn't seem like what I was thinking of when I first tagged that for review. Yes, proxy.

Changed May 24, 2011 09:48PM UTC by dmethvin comment:6

description: Callback functions e.g. for "fadeIn" often point at functions in objects. \ The problem is that "this" in that functions refere to the object which is manipulated in this case a html dom object. \ \ This is why we need parameter support for these callbacks so we can pass for example the original object or an id or whatever we want.\ \ Callback functions e.g. for "fadeIn" often point at functions in objects. \ The problem is that "this" in that functions refere to the object which is manipulated in this case a html dom object. \ \ This is why we need parameter support for these callbacks so we can pass for example the original object or an id or whatever we want. \ \

-1, Closure or proxy.

Changed June 03, 2011 02:01PM UTC by john comment:7

description: Callback functions e.g. for "fadeIn" often point at functions in objects. \ The problem is that "this" in that functions refere to the object which is manipulated in this case a html dom object. \ \ This is why we need parameter support for these callbacks so we can pass for example the original object or an id or whatever we want. \ \ Callback functions e.g. for "fadeIn" often point at functions in objects. \ The problem is that "this" in that functions refere to the object which is manipulated in this case a html dom object. \ \ This is why we need parameter support for these callbacks so we can pass for example the original object or an id or whatever we want.\ \

-1

Changed June 05, 2011 09:48PM UTC by ajpiano comment:8

description: Callback functions e.g. for "fadeIn" often point at functions in objects. \ The problem is that "this" in that functions refere to the object which is manipulated in this case a html dom object. \ \ This is why we need parameter support for these callbacks so we can pass for example the original object or an id or whatever we want.\ \ Callback functions e.g. for "fadeIn" often point at functions in objects. \ The problem is that "this" in that functions refere to the object which is manipulated in this case a html dom object. \ \ This is why we need parameter support for these callbacks so we can pass for example the original object or an id or whatever we want. \ \

-1 PROXY

Changed June 06, 2011 02:56PM UTC by scottgonzalez comment:9

description: Callback functions e.g. for "fadeIn" often point at functions in objects. \ The problem is that "this" in that functions refere to the object which is manipulated in this case a html dom object. \ \ This is why we need parameter support for these callbacks so we can pass for example the original object or an id or whatever we want. \ \ Callback functions e.g. for "fadeIn" often point at functions in objects. \ The problem is that "this" in that functions refere to the object which is manipulated in this case a html dom object. \ \ This is why we need parameter support for these callbacks so we can pass for example the original object or an id or whatever we want.\ \

-1, closures, proxies

Changed June 07, 2011 06:53PM UTC by rwaldron comment:10

milestone: 1.next1.7
resolution: → wontfix
status: openclosed

Closing per 1.7 roadmap meeting resolution