[wp-trac] [WordPress Trac] #50564: Update jQuery step two
WordPress Trac
noreply at wordpress.org
Thu Sep 3 06:30:06 UTC 2020
#50564: Update jQuery step two
--------------------------------+-------------------------
Reporter: azaozz | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: 5.6
Component: External Libraries | Version:
Severity: normal | Resolution:
Keywords: early needs-patch | Focuses: javascript
--------------------------------+-------------------------
Comment (by azaozz):
Replying to [comment:2 mgol]:
> Note that Migrate will not automatically restore previous behavior here
as we prefer Migrate to not reintroduce security issues by default.
Thanks for the clarification. Thinking it would be best if the WP
implementation leaves this out for now, i.e. keeps the security fix. Then,
if there are (lot of) problems during testing of WP 5.6, enable it
temporarily for one release cycle.
@TimothyBlynJacobs:
> If we upgrade to jQuery 3.0 do we anticipate using any jQuery 3.0
features?
This is a "tough question", but something we'll have to go through. A
good, backwards compatible way seems to be to not use any jQuery 3.x
features for (at least) the release cycle when jQuery is updated, i.e.
start using them in WP 5.7. That gives plenty of time to everybody to
update their code.
WP 5.7 is also the time to fix/refactor all core js to work without jQuery
Migrate 3.x. Currently there are several scripts that are not compatible.
This will also be the most "breaking" step, and will probably need some
safeguards in order to do it right.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/50564#comment:8>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list