#9285 closed bug (fixed)
custom trigger
Reported by: | anonymous | Owned by: | Rick Waldron |
---|---|---|---|
Priority: | low | Milestone: | 1.6.2 |
Component: | event | Version: | 1.6.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
$("#orderproduct").live('fill', function (e, i){
alert(i);
});
$("#orderproduct").trigger('fill', 0);
result: undefined (not 0)!!!
Change History (10)
comment:1 Changed 12 years ago by
Component: | unfiled → event |
---|---|
Owner: | set to anonymous |
Priority: | undecided → low |
Status: | new → pending |
comment:2 Changed 12 years ago by
Owner: | changed from anonymous to Rick Waldron |
---|---|
Status: | pending → assigned |
comment:4 Changed 12 years ago by
Milestone: | 1.next → 1.6.2 |
---|
comment:5 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Landing pull request 377. Check custom data != null(undefined), allows zero; Fixes #9285.
More Details:
comment:6 Changed 12 years ago by
Keywords: | needsdocs added |
---|
The docs page for .trigger()
says the data arg to trigger should be "An array of additional parameters to pass along to the event handler", but our consensus is that other things (particularly Objects) should be valid as well.
comment:8 Changed 12 years ago by
Keywords: | needsdocs removed |
---|
Note: See
TracTickets for help on using
tickets.
Thanks for taking the time to contribute to the jQuery project! Please provide a reduced test case on http://jsFiddle.net that reproduces the issue experienced to help us assess your ticket!
Additionally, test against the
jQuery (edge)
version to ensure the issue still exists.