Make WordPress Core

Opened 7 years ago

Last modified 3 years ago

#16494 closed enhancement

Remove "no conflict" mode from bundled jquery — at Version 3

Reported by: lloydbudd Owned by:
Milestone: Priority: low
Severity: minor Version: 3.1
Component: External Libraries Keywords: has-patch
Focuses: Cc:

Description (last modified by lloydbudd)

Remove "no conflict" mode from jquery

Over the last six months more and more of the themes I review for large sites have being using Google's CDN version of jquery (deregistering the bundled), not to get the benefit of CDN, but because most jquery libraries are dependent on $ and the developers don't know or want to deal with getting them to work in "no conflict".

I image we originally put in place "no conflict" mode for bundled jquery, as part of the transition from Prototype.

I appreciate it is hard to measure the impact of this type of change, but wanted to trac this all the same.

Additional Info



Change History (3)

#1 @nacin
7 years ago

This has the potential to break a lot. The $ variable is fought over by a few different libraries, Prototype definitely being one.

While I don't know the history, what we need is education for these developers. I don't think dumbing down our API is the best way to do it.

#2 @filosofo
7 years ago

I think Lloyd's suggestion is a good one. Working with theme designers, the most common JS error I see is related to their using jQuery plugins that assume $ is the jQuery object even in global scope.

And Prototype's been basically dead for years now.

The problem with educating developers is that typically the assumption is upstream, both in the plugin libraries and in the web tutorials, and the people using them don't have the knowledge necessary to make the changes.

#3 @lloydbudd
7 years ago

  • Description modified (diff)
Note: See TracTickets for help on using tickets.