[wp-trac] [WordPress Trac] #63821: Proposal: Drop support for IE conditional scripts and styles
WordPress Trac
noreply at wordpress.org
Tue Sep 23 07:31:58 UTC 2025
#63821: Proposal: Drop support for IE conditional scripts and styles
-------------------------------------------------+-------------------------
Reporter: jonsurrell | Owner: joedolson
Type: enhancement | Status: accepted
Priority: normal | Milestone: 6.9
Component: General | Version: 4.8
Severity: normal | Resolution:
Keywords: has-patch has-unit-tests needs-dev- | Focuses:
note needs-testing has-test-info | javascript, css
-------------------------------------------------+-------------------------
Comment (by rollybueno):
Replying to [comment:25 jonsurrell]:
> Isn't it safe to use notices liberally?
>
> I like that it surfaces conditional scripts and styles and makes it
clear that they should be removed.
>
> I really don't know whether this can be harmful or to what degree. My
inclination is to keep the notices. If there's precedent for silent
deprecation and/or you feel strongly that would be better for users, I
won't oppose removing the notices.
In my opinion, I think deprecation notices are the right way to go. They
do a good job of flagging scripts and styles that really shouldn’t be
hanging around anymore.
> On the other hand, this warning is a visible error flag for any site
that has debugging enabled in the environment.
I don't think we should worried about them showing up as error flags when
debugging is turned on, because well that’s exactly what debug mode is
for. Besides, debugging mode isn’t meant for production, so it’s on the
maintainer or site owner to handle those notices in their environment.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/63821#comment:26>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list