[wp-trac] [WordPress Trac] #56990: Render blocking CSS `classic-themes.css` unnecessarily enqueued

[WordPress Trac]

#56990: Render blocking CSS `classic-themes.css` unnecessarily enqueued
-------------------------------------+-------------------------------
 Reporter:  adamsilverstein          |       Owner:  flixos90
     Type:  defect (bug)             |      Status:  assigned
 Priority:  normal                   |   Milestone:  6.2
Component:  Themes                   |     Version:  6.1
 Severity:  normal                   |  Resolution:
 Keywords:  has-patch needs-testing  |     Focuses:  css, performance
-------------------------------------+-------------------------------
Changes (by flixos90):

 * owner:  (none) => flixos90
 * status:  new => assigned


Comment:

 @scruffian @adamsilverstein @wpgurudev I have opened
 https://github.com/WordPress/wordpress-develop/pull/4012, which I believe
 is a simpler fix to the most prevalent performance issue here, and it is a
 backward compatible change, which I think makes this a better solution
 than the previous patches. See the PR description for more context. Can
 you please take a look?

 I acknowledge that the perfect outcome here would be to not even load this
 CSS if no buttons are being used on the page, but as you are already
 saying @adamsilverstein, this is challenging to reliable determine in a
 classic theme. Since the amount of CSS here is tiny though, I don't really
 see that itself as a performance concern. The main problem is that the CSS
 is loaded via an external file, which adds unnecessary overhead that we
 can avoid by inlining it.

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