Use a higher priority on wp_head for inline custom CSS
|Reported by:||jeremyfelt||Owned by:||westonruter|
|Component:||Customize||Keywords:||has-patch commit fixed-major|
Other themes, well at least one, may also use priority 11 to output inline CSS for the same reasoning as our commit message - "so that it overrides any enqueued stylesheets". Because of the order in which these are added, the "overriding" custom CSS from WordPress it output before the additional theme styles.
The Jetpack solution, before WP 4.7, was to use priority 101 so that the styles were more likely to output last.
Because of the priority shifting/confusion, the upgrade to WordPress 4.7 caused visual regressions on the front end for at least 2 sites that I'm aware of.
If it's not too late, I'd like to suggest bumping this priority to something that fires even later, say 99.
Change History (12)
3 months ago
- Keywords fixed-major added
- Resolution fixed deleted
- Status changed from closed to reopened