Opened 20 months ago
Last modified 20 months ago
#62734 new defect (bug)
Regression in custom CSS loading order for `wp_enqueue_global_styles()`
| Reported by: | mukesh27 | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Awaiting Review |
| Component: | Editor | Version: | 6.7 |
| Severity: | normal | Keywords: | needs-patch dev-feedback has-screenshots |
| Cc: | Focuses: | css |
Description
In changeset [58703] / #61395, the behaviour of the wp_enqueue_global_styles() function was altered as part of WordPress 6.7. This change affects how global styles' custom CSS is output.
Previous behaviour (Before 6.7):
Global styles' custom CSS was appended at the end of the inline CSS, ensuring it loaded after individual block styles.
Current behaviour (After 6.7):
Following the changes introduced in [58703], the custom CSS now loads before the individual block styles, potentially affecting styling and overriding expectations for CSS specificity and hierarchy.
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png)
WP 6.6.2 behaviour