[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 needs-patch  |     Focuses:
----------------------------------------+--------------------------

Comment (by youknowriad):

 @westonruter Do you think the way the cascade works for the "additional
 CSS" in block themes should also work like classic themes?

 My understanding from checking the result here is that the priority issue
 is that the classic theme's style.css file is considered to have more
 priority than the customizer's additional CSS, which causes the issue.

 The reason for that is that the "additional CSS" in block themes is
 considered as part of the "theme styles" (so same level as style.css
 provided by a theme).

 But it seems the same issue can exist in block themes as well, but since
 most block theme styles use theme.json instead of style.css we didn't see
 it.

 I guess what I'm saying is that this is a not a new issue and that we
 should be thinking about the best path long term for this priority issue
 between "style.css" files and global styles regardless of theme.

 But to reduce the impact of the change here, I'm wondering if we should
 just make both block and classic themes load the "additional css" from the
 customizer with a higher priority or if we should just keep the fix for
 classic themes. (restore previous behavior). WDYT?

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