[wp-trac] [WordPress Trac] #57301: Emoji feature detection is incorrect

WordPress Trac noreply at wordpress.org
Fri Dec 9 22:18:47 UTC 2022


#57301: Emoji feature detection is incorrect
---------------------------+--------------------------------------
 Reporter:  sergiomdgomes  |       Owner:  (none)
     Type:  defect (bug)   |      Status:  new
 Priority:  normal         |   Milestone:  Awaiting Review
Component:  Emoji          |     Version:  trunk
 Severity:  normal         |  Resolution:
 Keywords:                 |     Focuses:  javascript, performance
---------------------------+--------------------------------------

Comment (by dmsnell):

 okay well oops, looking at the linked ticket it looks like the input list
 from Twemoji is stored as HTML hexadecimal character references, which
 might explain the confusion. The input is `&#x1f170`, representing code
 point U+1F170, as all hexadecimal character references have always
 referred to code points and not code units.

 Strangely, it looks like the previous code in
 [https://core.trac.wordpress.org/attachment/ticket/47852/47852.diff
 47852.diff] also used this representation and also referenced characters
 above the "code char" range (those code points which can be represented in
 UTF-16 without surrogate pairs).

 And also if that's the case, then I'm confused on how `fromCharCode`
 worked at all, lol, so I know I'm misunderstanding something. Is there
 something big I'm missing in the what the problem was or how it appeared
 in the linked patch?

 Is the effect that we've been saying for years that a given browser
 //doesn't// support Emoji when in fact it does?

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


More information about the wp-trac mailing list