Skip to main content

Bug Tracker

Side navigation

#12026 closed bug (fixed)

Opened July 05, 2012 09:17PM UTC

Closed July 05, 2012 09:26PM UTC

Last modified October 15, 2012 08:28PM UTC

Let $(html, props) use any jQuery.fn method

Reported by: dmethvin Owned by: dmethvin
Priority: low Milestone: 1.8
Component: core Version: 1.7.2
Keywords: Cc:
Blocked by: Blocking:

As discussed in IRC. Rather than keeping a separate .attrFn white list, allow $(html, props) to treat any property in jQuery.fn as callable.

Note that this does add some ambiguity as it now includes a large number of "reserved words" that previously were treated simply as attribute names. In addition, any 3rd-party plugins can now expand the proscribed namespace at runtime. For that reason, it is best to avoid the use of $(html, props) in production code. Instead, cover $(html, props) with a cool, slightly damp cloth and place it in your hacker's toolkit.

Bug reports against this new and awesome behavior should not be accepted.

Attachments (0)
Change History (3)

Changed July 05, 2012 09:17PM UTC by dmethvin comment:1

component: unfiledcore
keywords: → needsdocs
milestone: None1.8
owner: → dmethvin
priority: undecidedlow
status: newassigned

Changed July 05, 2012 09:26PM UTC by Dave Methvin comment:2

resolution: → fixed
status: assignedclosed

Fix #12026. Let props in $(html, props) be any jQuery.fn method.

Closes gh-839.

Changeset: cdd5132dcc02d4a3ff8df390677ffb8ff4b5a477

Changed October 15, 2012 08:28PM UTC by mikesherov comment:3

keywords: needsdocs