Skip to main content

Bug Tracker

Side navigation

#9285 closed bug (fixed)

Opened May 14, 2011 11:57AM UTC

Closed May 16, 2011 02:44PM UTC

Last modified March 08, 2012 06:07PM UTC

custom trigger

Reported by: anonymous Owned by: rwaldron
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)!!!

Attachments (0)
Change History (10)

Changed May 14, 2011 04:12PM UTC by addyosmani comment:1

component: unfiledevent
owner: → anonymous
priority: undecidedlow
status: newpending

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.

Changed May 14, 2011 09:08PM UTC by rwaldron comment:2

owner: anonymousrwaldron
status: pendingassigned

Changed May 14, 2011 09:53PM UTC by rwaldron comment:3

Changed May 16, 2011 02:42PM UTC by timmywil comment:4

milestone: 1.next1.6.2

Changed May 16, 2011 02:44PM UTC by Rick Waldron comment:5

resolution: → fixed
status: assignedclosed

Landing pull request 377. Check custom data != null(undefined), allows zero; Fixes #9285.

More Details:

Changeset: c17f589ec99e8309e813a4081eed47f39a0c6120

Changed May 16, 2011 08:39PM UTC by dmethvin comment:6

keywords: → needsdocs

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.

Changed May 16, 2011 08:51PM UTC by rwaldron comment:7

+1

Changed May 20, 2011 07:00PM UTC by dmethvin comment:8

keywords: needsdocs

Changed May 25, 2011 03:24PM UTC by timmywil comment:9

#9421 is a duplicate of this ticket.

Changed June 03, 2011 07:58PM UTC by rwaldron comment:10

#9511 is a duplicate of this ticket.