#14704 closed feature (wontfix)
Make .trigger() accept varargs to event data
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | undecided | Milestone: | None |
Component: | unfiled | Version: | 1.10.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Whenever I need to pass aditional parameters to .trigger(), I always feel that I could pass those as separate arguments after the event name, and not always as an array.
I'm not sure about backwards-compatibility issues though.
Change History (2)
comment:1 Changed 9 years ago by
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:2 Changed 9 years ago by
I agree, haven't thought about that.
It's not really a big issue actually, just 2 extra chars.
But thanks for the attention!
Note: See
TracTickets for help on using
tickets.
You're right. It is a back-compat issue.
Consider this case...
or worse...
To keep it simple, we've come to recommend that extra arguments always be passed in an array.