[wp-trac] [WordPress Trac] #64408: Global Styles: Lift restrictions on global styles for classic themes

[WordPress Trac]

#64408: Global Styles: Lift restrictions on global styles for classic themes
--------------------------------------+--------------------------
 Reporter:  youknowriad               |       Owner:  youknowriad
     Type:  enhancement               |      Status:  reopened
 Priority:  normal                    |   Milestone:  7.0
Component:  Themes                    |     Version:
 Severity:  normal                    |  Resolution:
 Keywords:  has-unit-tests has-patch  |     Focuses:
--------------------------------------+--------------------------

Comment (by westonruter):

 @youknowriad I worry about changing the position of either the Additional
 CSS coming from block themes or the Customizer. Sites have been developed
 with styles written in the context of a certain CSS cascade.

 That said, I'd feel less concerned if the Additional CSS in block themes
 were moved to be inserted at the very end of the cascade (as the
 Customizer was outputting at `wp_head` priority 101), with styles emitted
 at `wp_footer` notwithstanding. Since an author has written the Additional
 CSS in the Site Editor, presumably they would want it to override anything
 being emitted by core/themes/plugins. So it would seem safer to change the
 behavior in that direction. Either that, or just restore the previous
 behavior where the Additional CSS is located in different parts of the CSS
 cascade for block themes and classic themes.

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