[wp-trac] [WordPress Trac] #55628: Numerous console errors on Theme/Plugin File Editor screens and syntax highlighting not working

Mon Aug 19 13:53:41 UTC 2024

#55628: Numerous console errors on Theme/Plugin File Editor screens and syntax
highlighting not working
-------------------------------------------------+-------------------------
 Reporter:  ndiego                               |       Owner:
                                                 |  peterwilsoncc
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:  6.0
Component:  Script Loader                        |     Version:  6.0
 Severity:  normal                               |  Resolution:  fixed
 Keywords:  has-patch has-unit-tests dev-        |     Focuses:  javascript
  reviewed fixed-major                           |
-------------------------------------------------+-------------------------

Comment (by sergiomdgomes):

 Hey folks!

 I recently came across this issue when investigating why `wp-i18n` was
 being loaded in the `<head>` on a site. The cause seems to be the
 workaround for this bug (and #6195) that's
 [https://github.com/WordPress/gutenberg/blob/2862f2d1f169bea73e0550ff800d4ea121945a60/lib
 /client-assets.php#L61 still in place in Gutenberg].

 `wp-i18n` isn't too large a script, but it does depend on the considerably
 larger `wp-polyfill`, which as a result also gets enqueued in `<head>`.
 From a performance point of view, it would be a nice win if we managed to
 fix this in a different way, since scripts in the `<head>` are render-
 blocking and can thus have an impact on first paint and all subsequent
 paint metrics.

 I filed [https://github.com/WordPress/gutenberg/issues/64614 a bug in the
 Gutenberg repo] to track this as well.

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