From ad7456fe034a04c8cc7c08421b37754b188c5e6b Mon Sep 17 00:00:00 2001 From: Gary Pendergast Date: Mon, 16 Mar 2015 00:05:05 +0000 Subject: [PATCH] Emoji: Move a comment to match the restructure in [31779], and add an extra comment explaining how emoji rendering support is detected. See #31242 git-svn-id: https://develop.svn.wordpress.org/trunk@31788 602fd350-edb4-49c9-b593-d223f7449a82 --- src/wp-includes/js/wp-emoji.js | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/src/wp-includes/js/wp-emoji.js b/src/wp-includes/js/wp-emoji.js index 408cdf2d18..34b613b119 100644 --- a/src/wp-includes/js/wp-emoji.js +++ b/src/wp-includes/js/wp-emoji.js @@ -82,6 +82,11 @@ return false; } + /* + * Chrome on OS X added native emoji rendering in M41. Unfortunately, + * it doesn't work when the font is bolder than 500 weight. So, we + * check for bold rendering support to avoid invisible emoji in Chrome. + */ context.textBaseline = 'top'; context.font = '600 32px Arial'; @@ -99,9 +104,9 @@ return canvas.toDataURL().length > 3000; } else { /* - * Chrome on OS X added native emoji rendering in M41. Unfortunately, - * it doesn't work when the font is bolder than 500 weight. So, we - * check for bold rendering support to avoid invisible emoji in Chrome. + * This creates a smiling emoji, and checks to see if there is any image data in the + * center pixel. In browsers that don't support emoji, the character will be rendered + * as an empty square, so the center pixel will be blank. */ context.fillText( String.fromCharCode( 55357, 56835 ), 0, 0 ); return context.getImageData( 16, 16, 1, 1 ).data[0] !== 0;