[wp-trac] [WordPress Trac] #37110: Update to jQuery 3.*
WordPress Trac
noreply at wordpress.org
Fri Jul 31 15:46:41 UTC 2020
#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 |
-------------------------------------------------+-------------------------
Comment (by apedog):
The solutions posted above still treat this like it's a plugin-territory
problem. When it's the entire wp-core admin-side breaking. These plugins
will break wp-core's {{{common.js}}} functionality.
Even if most offending plugins will promptly fix this, not everyone has
automatic updates set on their site/plugins. And I'm not sure how many
will opt-in after 5.5 will have introduced this break.
I've no idea about the amount of work needed to create a wp version of
{{{jquery-migrate}}} that logs {{{_doing_it_wrong}}} messages to console.
But I know installations will break. Not everyone can do the whole Health
Check & Troubleshooting process and find the offending plugin. They'll
just know their site broke when updating to 5.5 (which it will have).
IMO {{{jquery-migrate}}} could be kept at least for this cycle. Preferably
with {{{_doing_it_wrong}}} messaging to allow for a smoother transition
down the line (if that's something that can be introduced in time).
At the very least a {{{.live()}}} (the most likely offender) should be
polyfilled for 5.5 - with debug console logs to alert plugin devs for a
whole cycle.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/37110#comment:149>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list