[wp-trac] [WordPress Trac] #65336: global-styles-inline-css cannot be removed since 7.0
WordPress Trac
noreply at wordpress.org
Thu Jun 4 10:34:04 UTC 2026
#65336: global-styles-inline-css cannot be removed since 7.0
-------------------------------------------------+-------------------------
Reporter: edent | Owner:
| westonruter
Type: defect (bug) | Status: accepted
Priority: normal | Milestone: 7.0.1
Component: General | Version: 7.0
Severity: normal | Resolution:
Keywords: has-patch has-unit-tests reporter- | Focuses: css
feedback |
-------------------------------------------------+-------------------------
Comment (by edent):
Replying to [comment:4 wildworks]:
> To prevent the enqueuing of global styles CSS in WordPress 7.0, you can
use either of the following code snippets:
Or, perhaps, themes could opt in to this new functionality. That would
reduce the support burden for sites running older themes or who don't need
this functionality.
> Personally, I'm unsure if we should be responsible for backward
compatibility regarding CSS enqueue changes. Similar modifications should
have been made many times in the past.
Personally, I think WordPress should be responsible for not introducing
breaking changes. This happens frequently with WordPress updates and is
always resolved by the project eventually relenting and patching the
undesirable behaviour.
> I'm not sure if it's worth adding such special handling to
`wp_enqueue_global_styles()` for the sake of backward compatibility.
I'm not sure if WordPress should be introducing code which breaks or
disrupts their users' sites.
I think I am being reasonable. Don't break users' sites. Test new
functionality. If you really dont want to make new things opt-in, then at
least make it trivial to opt-out - preferably in a documented and
consistent manner.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/65336#comment:6>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list