Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #55126, comment 3


Ignore:
Timestamp:
02/09/2022 05:34:03 PM (3 years ago)
Author:
sergiomdgomes
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #55126, comment 3

    initial v1  
    1 An alternative approach to preserving IE 11 compatibility is to use a `wp_get_script_polyfill`-based approach [https://github.com/WordPress/wordpress-develop/blob/6192591757bb1237be0d234943399bcc88e44a6f/src/wp-content/themes/twentytwentyone/functions.php#L439-L447 / like Twenty Twenty One does].
     1An alternative approach to preserving IE 11 compatibility is to use a `wp_get_script_polyfill`-based approach [https://github.com/WordPress/wordpress-develop/blob/6192591757bb1237be0d234943399bcc88e44a6f/src/wp-content/themes/twentytwentyone/functions.php#L439-L447 / like Twenty Twenty One does]. Thank you for pointing me to this, @gziolo!
    22
    33This would keep the code clean and would prevent polyfills / helper functions from being loaded in modern browsers, but the downside would be that it would require bumping up compatibility to WordPress 5.0.