Changes between Initial Version and Version 1 of Ticket #57301, comment 28
- Timestamp:
- 02/03/2023 12:11:34 AM (2 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #57301, comment 28
initial v1 11 11 Looks like the attached pictures appeared inline so I won't copy them here into the instructions, but I have provided screenshots of tests in Safari, Firefox, and Chrome on macOS. Additionally I tested this on IE5 in Windows 98 but before and after both reported no support for the Emoji, which isn't surprising because that support is missing. Still, the page did not crash, which is the more important aspect of testing. 12 12 13 Since I could not open the dev tools in IE 5 I loaded this script instead, which directly serves the Emoji detector outside of WordPress, which is also usable in any browser. Fun fact, `JSON.stringify()` and `Object.keys()` are not supported in IE 5 14 15 {{{#!php 16 <?php 17 // test.php 18 <script>_wpemojiSettings = { supports: {} };</script> 19 <script src="wp-includes/js/wp-emoji-loader.js"></script> 20 <script> 21 setTimeout( function() { 22 var e = document.createElement('pre'); 23 var keys = ['everything', 'everythingExceptFlag', 'flag', 'emoji']; 24 25 for ( i = 0; i < keys.length; i++ ) { 26 e.innerHTML += keys[i] + ": " + _wpemojiSettings.supports[ keys[i] ] + "<br>\n"; 27 }; 28 document.body.appendChild( e ); 29 }, 1000 ); 30 </script> 31 }}} 32 33 13 34 For mixed-support testing one needs to examine this on an OS that is old enough to lack more recent Unicode updates, but I don't think that part of the code has been under scrutiny or change, whereas the change is mostly isolated to fixing two things: 14 35 - there was an outright bug in adding code points outside of the Basic Multilingual Plane which `fromCharCode` cannot properly translate