[wp-trac] [WordPress Trac] #22896: Prevent plugins from overriding jQuery in the admin

WordPress Trac noreply at wordpress.org
Thu Dec 13 19:47:38 UTC 2012


#22896: Prevent plugins from overriding jQuery in the admin
--------------------------------+------------------
 Reporter:  nacin               |       Owner:
     Type:  enhancement         |      Status:  new
 Priority:  normal              |   Milestone:  3.6
Component:  External Libraries  |     Version:
 Severity:  normal              |  Resolution:
 Keywords:  dev-feedback        |
--------------------------------+------------------
Changes (by kevinjohngallagher):

 * cc: kevinjohngallagher (added)
 * type:  defect (bug) => enhancement


Comment:

 My concern with things like this is that it's a fairly sweeping
 functionality change, and a lockdown, that has the potential to have an
 incredibly large impact; especially for those not using WordPress in a
 "traditional" way.  I completely understand that we're the smallest fish
 in the sea here, but we haven't developed a WP theme in at least 18
 months; while almost all of our WP work in the last 2.5 years has come
 from backend customisation and integration. This would (potentially) put a
 major dent in that.


 Replying to [comment:5 helenyhou]:
 > Replying to [comment:4 ipstenu]:
 > > We have to keep in mind legitimate use cases
 >
 > This does say "in the admin", in which case there is no legitimate
 reason to load jQuery from elsewhere :)

 I think we can all admit that with 17 million WP installs out there, the
 idea that not one of them has a "legitimate reason" for ''anything'' seems
 unrealistic.

 Here's a few off the top of my head:

 * IE6 support
 * SLA compliance
 * Digital Security compliance
 * Regression testing
 * Customised SaaS offerings
 * Reliance on external code
 * Not moving to jQuery 2.0 next release - thats a huge fear right now (no
 IE6/7/8 support)
 .


 Replying to [comment:7 F J Kaiser]:
 >
 > ''But maybe there's another possibility:'' Make {{{_doing_it_wrong()}}}
 non disable-able with {{{WP_DEBUG}}}, so everybody (incl. customers of so-
 called "premium"-plugins/-themes) start being aware of the crap they just
 have installed.
 >

 Customers don't care about "the crap they just have installed" from an
 elitist developer perspective. They just want something that works. We
 have to start thinking of the actual user, and not just get on our high
 horse because someone is doing something that is wrong in our opinion.
 .


 > Anyway, I'm in for that (or any related) change, no matter at which
 cost. At those who want to change the "type" away from "defect/bug": Dare
 to.

 Done.
 This is not a bug.
 It's working as intended.
 It's the very definition of an Enhancement.
 I can see some reasons why people want it, thats grand.
 But it's not a bug, as the code works just fine as is :)

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


More information about the wp-trac mailing list