[wp-trac] [WordPress Trac] #64174: deprecation notice for conditional scripts

WordPress Trac noreply at wordpress.org
Mon Nov 10 22:50:13 UTC 2025


#64174: deprecation notice for conditional scripts
-------------------------------------+------------------------------
 Reporter:  hupe13                   |       Owner:  (none)
     Type:  defect (bug)             |      Status:  new
 Priority:  normal                   |   Milestone:  6.9
Component:  General                  |     Version:  trunk
 Severity:  normal                   |  Resolution:
 Keywords:  2nd-opinion needs-patch  |     Focuses:  javascript, css
-------------------------------------+------------------------------
Changes (by peterwilsoncc):

 * focuses:   => javascript, css


Comment:

 I've been going back and forth on this, and will probably continue to.

 Ultimately, I don't think it's wise to suppress the errors and silently
 deprecate as it's very important developers be aware that their scripts
 and styles are not been enqueued if they have IE conditional data.

 Only calling `_deprecated_argument()` if `SCRIPT_DEBUG` is enabled would
 be problematic for development plugins, such as Query Monitor, as the
 notice would be suppressed from them too as they typically use the
 `deprecated_argument_run` hook to collect messages.

 If `deprecated_argument_trigger_error` and related filters passed the
 `$function_name, $version, $message = ''` arguments, it might be possible
 to use `SCRIPT_DEBUG` on the filter but it's a little too late to add that
 for the 6.9 cycle.

 tl;dr: I think it's best to close this ticket as unplanned/wontfix.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/64174#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list