[wp-trac] [WordPress Trac] #37817: Emoji code not loaded responsibly

[WordPress Trac]

#37817: Emoji code not loaded responsibly
---------------------------+----------------------------
 Reporter:  superpoincare  |       Owner:  peterwilsoncc
     Type:  enhancement    |      Status:  assigned
 Priority:  normal         |   Milestone:  4.7
Component:  Emoji          |     Version:  4.6
 Severity:  normal         |  Resolution:
 Keywords:  has-patch      |     Focuses:  performance
---------------------------+----------------------------

Comment (by superpoincare):

 Hi Peter,

 Yeah makes sense. I did some tests: with 4.6.1, 4.6.1 with emoji disabled
 and 4.7-alpha with your diff.

 The way I used your diff was by upgrading to the alpha-channel using the
 beta tester plugin, disabling emoji with remove_action and adding the
 inline emoji JS by hand in the child theme by manually minifying the
 latest code (from your diff) with uglifyjs2

 Shows good improvement. The way I was experimenting as I mentioned before
 was to see when fonts files are actually loaded after the Google fonts css
 is downloaded: since fonts are loaded when the browser can decide which
 ones to download, one can observe if emoji loader is interfering CSSOM/DOM
 construction.

 The result is here:
 http://www.webpagetest.org/video/compare.php?tests=161016_VZ_cff2dbe633cda84a18207adc37c2d352,161016_MH_077d7f6a83db076a2bb2e69f2a6b1f64,161016_8Y_595b5692971777c061696893035783b4#


 The fonts are fetched almost immediately once the css is loaded in the
 latest code, which suggests that there's good improvement.

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