Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

execute()'s callback doesn't fire #1

Closed
mscdex opened this issue Apr 30, 2010 · 1 comment
Closed

execute()'s callback doesn't fire #1

mscdex opened this issue Apr 30, 2010 · 1 comment
Labels
bug

Comments

@mscdex
Copy link
Owner

mscdex commented Apr 30, 2010

execute()'s callback currently doesn't fire due to Javascript claiming the type of the function passed in is always 'undefined'?

I haven't been able to find out the cause of this. The same 'undefined' error occurs no matter what type of object is passed in for the optional parameter.
@mscdex
Copy link
Owner Author

mscdex commented May 1, 2010

execute()'s optional callback parameter now fires correctly. Closed by f6f1b40.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mscdex