Side navigation
#12602 closed bug (notabug)
Opened September 24, 2012 09:46PM UTC
Closed September 24, 2012 09:56PM UTC
Last modified September 25, 2012 06:10AM UTC
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.
Attachments (0)
Change History (3)
Changed September 24, 2012 09:56PM UTC by comment:1
| resolution: | → notabug |
|---|---|
| status: | new → closed |
Changed September 24, 2012 10:00PM UTC by comment:2
Blitzed.
FWIW, this is how it's used http://jsfiddle.net/rwaldron/ssYk4/
Changed September 25, 2012 06:10AM UTC by comment:3
| _comment0: | ok, totally valid. ... and it is so hard to add a signature for that because? \ \ heck, just do $.selector → 1348553533287903 |
|---|
ok, totally valid. ... and it is so hard to add a signature for that because?
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.