[wp-trac] [WordPress Trac] #62882: "Navigation Block CSS (style.min.css) Loads Even When Gutenberg is Disabled"

[WordPress Trac]

#62882: "Navigation Block CSS (style.min.css) Loads Even When Gutenberg is
Disabled"
--------------------------+-------------------------------
 Reporter:  jvrajput420   |       Owner:  (none)
     Type:  defect (bug)  |      Status:  closed
 Priority:  normal        |   Milestone:
Component:  Editor        |     Version:
 Severity:  normal        |  Resolution:  invalid
 Keywords:                |     Focuses:  css, performance
--------------------------+-------------------------------
Changes (by flixos90):

 * keywords:  close =>
 * status:  assigned => closed
 * resolution:   => invalid
 * milestone:  Awaiting Review =>


Comment:

 @jvrajput420 Thank you for raising this, and for the thoughtful
 discussion.

 I tend to agree with @sabernhardt that this is not really the concern of
 Core. In terms of Core itself, the block editor is the only way to use it,
 and Core technical decisions are made with that in mind.

 While Core already provides mechanisms to only load certain CSS and
 JavaScript when it is actually used, by default this only works for block
 themes since for classic themes there are limitations that make reliable
 detection impossible. This is probably why you see CSS enqueued that is
 not used (since given your site uses the Classic Editor plugin, it must be
 using a classic theme).

 Catering for an experience that assumes Gutenberg is not there is plugin
 territory, which is why plugins like "Classic Editor" and "Disable
 Gutenberg" exist. The first caters for the editing experience, while the
 latter caters for disabling "as much as possible" from what Gutenberg
 provides beyond the editing experience.

 As such, I'm going to close this due to being plugin territory.

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