Bug Tracker

Opened 5 years ago

Closed 5 years ago

Last modified 4 years ago

#12026 closed bug (fixed)

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.

Change History (3)

comment:1 Changed 5 years ago by dmethvin

  • Component changed from unfiled to core
  • Keywords needsdocs added
  • Milestone changed from None to 1.8
  • Owner set to dmethvin
  • Priority changed from undecided to low
  • Status changed from new to assigned

comment:2 Changed 5 years ago by Dave Methvin

  • Resolution set to fixed
  • Status changed from assigned to closed

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

Closes gh-839.

Changeset: cdd5132dcc02d4a3ff8df390677ffb8ff4b5a477

comment:3 Changed 4 years ago by mikesherov

  • Keywords needsdocs removed
Note: See TracTickets for help on using tickets.