[wp-trac] [WordPress Trac] #16494: Remove "no conflict" mode from bundled jquery

WordPress Trac wp-trac at lists.automattic.com
Thu Feb 10 14:33:54 UTC 2011


#16494: Remove "no conflict" mode from bundled jquery
--------------------------------+------------------------------
 Reporter:  lloydbudd           |       Owner:
     Type:  enhancement         |      Status:  new
 Priority:  low                 |   Milestone:  Awaiting Review
Component:  External Libraries  |     Version:  3.1
 Severity:  minor               |  Resolution:
 Keywords:                      |
--------------------------------+------------------------------

Comment (by aaroncampbell):

 I'm all for being cautious and thinking this through some, but my gut
 reaction is that I'd like to see no conflict go away.  While ericmann is
 correct that the "most basic tutorials available from the jQuery team" has
 it right, there are also thousands of other tutorials spread across the
 web that people follow, which don't.  Then people are frustrated because
 the code that they are copying/pasting doesn't work on WordPress, but does
 in other places...which is key because it focuses their frustration on WP
 not on the tutorial author.

 Think about a new developer who's code doesn't work until he stops using
 WordPress's bundled jQuery and starts using Googles.  Not to mention it
 *is* a way to lower the barrier to entry for WP developers, which we
 always like to do.

 Maybe we need to leave an option (a constant or a filter, nothing in the
 ui) that would allow a user to force it into noConflict like it is now.
 This way if they needed MooTools instead of jQuery (and they couldn't do
 something like noConflict in MooTools...I don't know that library very
 well), they could simply make the adjustment.

 @scribu - Pass the popcorn.

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/16494#comment:8>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list