Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #12009, comment 115


Ignore:
Timestamp:
05/29/2023 11:05:26 AM (14 months ago)
Author:
azaozz
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #12009, comment 115

    initial v1  
    77
    88However the above is not the only reason to remove that code. There are other reasons:
    9 1. This is not used in core. Adding untested and unconfirmed API methods to core is a bit red flag. The "unconfirmed" part refers to usability, i.e. if that method is not used in core, would it at least be useful to at least 10% of the plugins that use Script Loader? As far as I see this is a "NO".
     91. This is not used in core. Adding untested and unconfirmed API methods to core is a big red flag. The "unconfirmed" part refers to usability, i.e. if that method is not used in core, would it at least be useful to at least 10% of the plugins that use Script Loader? As far as I see this is a "NO".
    1010
    1111> This goes back to why inline scripts were introduced in the first place. There needs to be a way to pass dynamic data from PHP back to static JS scripts that can execute either before or after a registered script.