[wp-trac] [WordPress Trac] #37110: Update to jQuery 3.*

[WordPress Trac]

#37110: Update to jQuery 3.*
-------------------------------------------------+-------------------------
 Reporter:  jorbin                               |       Owner:  (none)
     Type:  task (blessed)                       |      Status:  reopened
 Priority:  normal                               |   Milestone:  5.5
Component:  External Libraries                   |     Version:
 Severity:  critical                             |  Resolution:
 Keywords:  early has-patch needs-testing        |     Focuses:  javascript
  needs-screenshots has-dev-note commit          |
-------------------------------------------------+-------------------------

Comment (by desrosj):

 Replying to [comment:159 azaozz]:
 > True. At the same time letting `jquery-migrate` be enqueued separately
 (instead of `jquery`) will bring problems/make things messier in the
 future, when jQuery Migrate is updated.

 I think I feel the same way about this as I do about intentionally adding
 the migrate enqueue. Expecting migrate to be updated the future is
 something that would then be expected.

 > - Add support for direct enqueuing of jQuery Migrate "temporarily" only
 for 5.5, then remove it in 5.6. This will break all plugins and themes
 that still use it at that time.

 The current plan is to remove migrate after the jQuery update is shipped
 (which would be the more likely breaking change). Calling
 `wp_enqueue_script()` on an unregistered script would just result in
 nothing happening.

 > - Add support for migrate and keep it in core "forever". This will make
 it even harder to update jQuery in the future, almost impossible,
 considering that some plugins will expect some versions of jQuery with
 some versions of Migrate, others will expect different

 If we can get jQuery to the latest version, and then update every time
 there is a release, we can bring jQuery more inline with how other
 External Libraries are maintained, with an expectation that you keep
 plugin code up to date. We include external libraries all the time that
 potentially have breaking changes. The difference is that they are updated
 regularly. I don't know why we couldn't establish the same pattern here.

 > Not sure what kind of "aggressive outreach" you have in mind, thinking a
 good example would be to have a postbox on the dashboards of all WP
 installs that still have old scripts.

 "emailing plugin and theme authors directly, and often" was what I had in
 mind initially. This could also be combined with any combination of a
 WordPress.org News post calling this out, outreach to various WP related
 news sources with requests to publish articles, maybe WordCamp talks or
 workshops helping devs update, etc. The exact communication plan could be
 discussed and refined to ensure maximum reach.

 @archon810 sorry, I am not aware of a way to unsubscribe from a ticket
 when you have commented on it previously.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37110#comment:160>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform