WordPress.org

Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #37110, comment 155


Ignore:
Timestamp:
07/31/2020 04:50:18 PM (8 weeks ago)
Author:
azaozz
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #37110, comment 155

    initial v1  
    1212> Of course, we would rather developers update their code to be compatible with newer versions of jQuery instead, but it's not unreasonable to expect that some may just need more time. This can only be a temporary fix for them anyway, because step 2 of the roadmap is to update `jquery-migrate` to the most recent version.
    1313
    14 Right. jQuery 3.x plus jQuery Migrate 3.x (WP 5.6) will not be backwards compatible with super old code. Then require step 5 of this list: https://jquery.com/upgrade-guide/3.0/#jquery-migrate-plugin (latest 1.x without migrate).
     14Right. jQuery 3.x plus jQuery Migrate 3.x (WP 5.6) will not be backwards compatible with super old code. They require step 5 of this list: https://jquery.com/upgrade-guide/3.0/#jquery-migrate-plugin (latest 1.x without migrate).
    1515
    1616Been thinking about what would be the best way to give more time to both plugin/theme authors and users. Perhaps making a simple "back-compat" plugin and releasing it with 5.5 would serve that purpose? As far as I see the plugin can be "fully automatic", detect what version of WP is used and enqueue/change scripts as needed.