Skip to main content

Bug Tracker

Side navigation

#11101 closed bug (fixed)

Opened December 24, 2011 04:42PM UTC

Closed June 11, 2012 10:10PM UTC

Deprecate "exclusive" events option from trigger method

Reported by: jzaefferer Owned by: dmethvin
Priority: low Milestone: 1.8
Component: event Version: 1.7.1
Keywords: Cc: dmethvin
Blocked by: Blocking:

Apparently trigger allows you to specify to trigger only non-namespaced events, via .trigger("click!"). Here's the implementation: (line 250-254)

I don't see any mention of that in the documentation:

So either it should either be removed or documented.

Attachments (0)
Change History (5)

Changed December 26, 2011 01:52PM UTC by addyosmani comment:1

cc: → DaveMethvin
component: unfiledeffects
keywords: → needsreview
priority: undecidedlow

Adding needsreview. I personally think this should be documented, however if there's a good reason it hasn't been to date, it would be interesting to find out what it is :)

Changed December 26, 2011 02:57PM UTC by dmethvin comment:2

cc: DaveMethvindmethvin
component: effectsevent
keywords: needsreview
owner: → dmethvin
status: newassigned

We use exclusive events internally, in data events. However we've talked about deprecating those and when we remove them we can also remove exclusive events. That would be my preference.

These have never been in the formal documentation but have been mentioned in a few places:

Changed March 03, 2012 10:29PM UTC by dmethvin comment:3

milestone: None1.8

Changed May 07, 2012 02:54PM UTC by dmethvin comment:4

summary: Document or remove exclusive events option from trigger methodDeprecate "exclusive" events option from trigger method

Changed June 11, 2012 10:10PM UTC by dmethvin comment:5

resolution: → fixed
status: assignedclosed

I will mark this as done since there are no docs changes. This ticket will serve as notice. Removal will be done as a separate ticket in 1.9.