[wp-trac] [WordPress Trac] #21170: JavaScript actions and filters

[WordPress Trac]

#21170: JavaScript actions and filters
----------------------------+--------------------------
 Reporter:  koopersmith     |       Owner:  koopersmith
     Type:  task (blessed)  |      Status:  new
 Priority:  normal          |   Milestone:  3.5
Component:  General         |     Version:  3.4
 Severity:  normal          |  Resolution:
 Keywords:                  |
----------------------------+--------------------------

Comment (by vhauri):

 @azaozz The above script is a maintained plugin that is being constantly
 changed (i.e. it is itself the dependency). I'm not sure how we'd maintain
 cross-compatibility with it, but if your thought is that we use it as a
 basis for a vanilla JS library (one that doesn't maintain any sort of
 compatibility with the latest and greatest version of AmplifyJS) that does
 the actions/hooks stuff, that sounds reasonable. My preference for basing
 off jQuery is that the Callbacks object will likely be maintained for us,
 so code that utilizes it will also be somewhat future-proof. I'm just not
 sure whether that'll be the case for AmplifyJS, but obviously if we're
 just using the codebase as it stands now as a branching point, no issues.

 I think this speaks to the larger issue of whether jQuery itself should be
 assumed. Your point about the front-end (i.e. in comment-reply.js) does
 make me think that maybe there's a need to separate this from jQuery,
 although I do feel that jQuery is the de-facto JS library that WP uses at
 this point.

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