#12602 closed bug (notabug)
passing data argument to .on() fails (1.8.1 vs. 1.8.2 regression)
Reported by: | latchkey | Owned by: | |
---|---|---|---|
Priority: | undecided | Milestone: | None |
Component: | unfiled | Version: | 1.8.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
The only difference between the two blocks is the optional [data] argument to .on()
ie:
formFoo.on('keyup.foo', inputsFoo, checkerFoo); formBar.on('keyup.bar', inputsBar, {'bar':1}, checkerBar); Both work fine with 1.8.1.
Change History (3)
comment:1 Changed 11 years ago by
Resolution: | → notabug |
---|---|
Status: | new → closed |
comment:2 Changed 11 years ago by
Blitzed.
FWIW, this is how it's used http://jsfiddle.net/rwaldron/ssYk4/
comment:3 Changed 10 years ago by
ok, totally valid. ... and it is so hard to add a signature for that because?
heck, just do $.selector
Version 0, edited 10 years ago
by
(next)
Note: See
TracTickets for help on using
tickets.
There is no signature for
.on()
that takes a jQuery object as its second argument. http://api.jquery.com/onPlease ask for help on the forum for the followup "Then why did this work before?", or simply use a debugger to see what it is doing.