Some of http://www.unicode.org/Public/emoji/5.0/emoji-test.txt are not displayed correctly

Issue #13583622 • Assigned to wptcomptri@microsoft.com

Details

Author
Richard S.
Created
Sep 5, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
16.16281
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

View http://www.unicode.org/Public/emoji/5.0/emoji-test.txt in 16281. The following are not displayed correctly. Strangely, the keycaps, and only these, display correctly here while I compose this even though they display incorrectly in the TXT file URL.

263A FE0F ; fully-qualified # ☺️ smiling face
263A ; non-fully-qualified # ☺ smiling face

1F575 FE0F 200D 2642 FE0F ; fully-qualified # 🕵️‍♂️ man detective

1F575 FE0F 200D 2642 ; non-fully-qualified # 🕵️‍♂ man detective

1F575 FE0F 200D 2640 FE0F ; fully-qualified # 🕵️‍♀️ woman detective

1F575 FE0F 200D 2640 ; non-fully-qualified # 🕵️‍♀ woman detective

1F3CC FE0F 200D 2642 FE0F ; fully-qualified # 🏌️‍♂️ man golfing

1F3CC FE0F 200D 2642 ; non-fully-qualified # 🏌️‍♂ man golfing

1F3CC FE0F 200D 2640 FE0F ; fully-qualified # 🏌️‍♀️ woman golfing

1F3CC FE0F 200D 2640 ; non-fully-qualified # 🏌️‍♀ woman golfing

26F9 FE0F 200D 2642 FE0F ; fully-qualified # ⛹️‍♂️ man bouncing ball

26F9 FE0F 200D 2642 ; non-fully-qualified # ⛹️‍♂ man bouncing ball

26F9 FE0F 200D 2640 FE0F ; fully-qualified # ⛹️‍♀️ woman bouncing ball

26F9 FE0F 200D 2640 ; non-fully-qualified # ⛹️‍♀ woman bouncing ball

1F3CB FE0F 200D 2642 FE0F ; fully-qualified # 🏋️‍♂️ man lifting weights

1F3CB FE0F 200D 2642 ; non-fully-qualified # 🏋️‍♂ man lifting weights

1F3CB FE0F 200D 2640 FE0F ; fully-qualified # 🏋️‍♀️ woman lifting weights

1F3CB FE0F 200D 2640 ; non-fully-qualified # 🏋️‍♀ woman lifting weights

1F469 200D 2764 FE0F 200D 1F48B 200D 1F468 ; fully-qualified # 👩‍❤️‍💋‍👨 kiss: woman, man

1F468 200D 2764 FE0F 200D 1F48B 200D 1F468 ; fully-qualified # 👨‍❤️‍💋‍👨 kiss: man, man

1F469 200D 2764 FE0F 200D 1F48B 200D 1F469 ; fully-qualified # 👩‍❤️‍💋‍👩 kiss: woman, woman

1F469 200D 2764 FE0F 200D 1F468 ; fully-qualified # 👩‍❤️‍👨 couple with heart: woman, man

1F468 200D 2764 FE0F 200D 1F468 ; fully-qualified # 👨‍❤️‍👨 couple with heart: man, man

1F469 200D 2764 FE0F 200D 1F469 ; fully-qualified # 👩‍❤️‍👩 couple with heart: woman, woman

1F441 FE0F 200D 1F5E8 FE0F ; fully-qualified # 👁️‍🗨️ eye in speech bubble

1F441 FE0F 200D 1F5E8 ; non-fully-qualified # 👁️‍🗨 eye in speech bubble

2660 FE0F ; fully-qualified # ♠️ spade suit
2660 ; non-fully-qualified # ♠ spade suit
2665 FE0F ; fully-qualified # ♥️ heart suit
2665 ; non-fully-qualified # ♥ heart suit
2666 FE0F ; fully-qualified # ♦️ diamond suit
2666 ; non-fully-qualified # ♦ diamond suit
2663 FE0F ; fully-qualified # ♣️ club suit
2663 ; non-fully-qualified # ♣ club suit

2195 FE0F ; fully-qualified # ↕️ up-down arrow
2195 ; non-fully-qualified # ↕ up-down arrow
2194 FE0F ; fully-qualified # ↔️ left-right arrow
2194 ; non-fully-qualified # ↔ left-right arrow

2640 FE0F ; fully-qualified # ♀️ female sign
2640 ; non-fully-qualified # ♀ female sign
2642 FE0F ; fully-qualified # ♂️ male sign
2642 ; non-fully-qualified # ♂ male sign

203C FE0F ; fully-qualified # ‼️ double exclamation mark
203C ; non-fully-qualified # ‼ double exclamation mark

00A9 FE0F ; fully-qualified # ©️ copyright
00A9 ; non-fully-qualified # © copyright
00AE FE0F ; fully-qualified # ®️ registered
00AE ; non-fully-qualified # ® registered
2122 FE0F ; fully-qualified # ™️ trade mark
2122 ; non-fully-qualified # ™ trade mark

0023 FE0F 20E3 ; fully-qualified # #️⃣ keycap: #
0023 20E3 ; non-fully-qualified # #⃣ keycap: #
002A FE0F 20E3 ; fully-qualified # *️⃣ keycap: *
002A 20E3 ; non-fully-qualified # *⃣ keycap: *
0030 FE0F 20E3 ; fully-qualified # 0️⃣ keycap: 0
0030 20E3 ; non-fully-qualified # 0⃣ keycap: 0
0031 FE0F 20E3 ; fully-qualified # 1️⃣ keycap: 1
0031 20E3 ; non-fully-qualified # 1⃣ keycap: 1
0032 FE0F 20E3 ; fully-qualified # 2️⃣ keycap: 2
0032 20E3 ; non-fully-qualified # 2⃣ keycap: 2
0033 FE0F 20E3 ; fully-qualified # 3️⃣ keycap: 3
0033 20E3 ; non-fully-qualified # 3⃣ keycap: 3
0034 FE0F 20E3 ; fully-qualified # 4️⃣ keycap: 4
0034 20E3 ; non-fully-qualified # 4⃣ keycap: 4
0035 FE0F 20E3 ; fully-qualified # 5️⃣ keycap: 5
0035 20E3 ; non-fully-qualified # 5⃣ keycap: 5
0036 FE0F 20E3 ; fully-qualified # 6️⃣ keycap: 6
0036 20E3 ; non-fully-qualified # 6⃣ keycap: 6
0037 FE0F 20E3 ; fully-qualified # 7️⃣ keycap: 7
0037 20E3 ; non-fully-qualified # 7⃣ keycap: 7
0038 FE0F 20E3 ; fully-qualified # 8️⃣ keycap: 8
0038 20E3 ; non-fully-qualified # 8⃣ keycap: 8
0039 FE0F 20E3 ; fully-qualified # 9️⃣ keycap: 9
0039 20E3 ; non-fully-qualified # 9⃣ keycap: 9

Attachments

Comments and activity

  • The keycap characters also display correctly here when viewing the bug but still incorrectly in the TXT file. One exception is the * keycaps for which the enclosing box is too small and has no space before the k in keycap.

    002A FE0F 20E3 ; fully-qualified # *️⃣ keycap: *
    002A 20E3 ; non-fully-qualified # *⃣ keycap: *

    I included the fully and non-fully qualified variants of the range from 2660 to 2122 only to show both the text and emoji presentation. These default to text presentation so the non-fully qualified are displayed correctly. It is the fully qualified forms that should use the emoji presentation but do not.

  • Microsoft Edge Team

    Changed Assigned To to “Steven K.”

  • I noted these issues in another emoji issue as well. In 16296, the gendered emoji are now correct. All the rest are bad for the fully qualified forms which have an explicit emoji presentation. The text presentation is OK for those since they all default to text with the exception of the key cap sequences. Those look horrible the emoji-test file but that may be a font issue.

  • The keycap problems are an Edge issue. Chrome 61 on RS3 16296 displays the fully qualified variants correctly. The non-fully qualified keycaps are as bad as they are in Edge and that may be a font issue.

  • Hi Richard,

    I wanted to let you know that work has been done on all of the issues with the 5.0 emjoi-test.txt test page you mentioned.  My testing of that page in a recent development build shows every emoji rendering correctly.  This also includes the fully-qualified and non-fully-qualified sequences and the keycaps.

    Also, the work to correct the issue you mention here, was completed while correcting the bug report you submitted for the zero width joiner sequences/gendered emoji.

    https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/12952367/

    Appreciate this submission and helping getting these emoji all working properly.  Your submissions helped get these corrected.

    The MS Edge Team

  • Microsoft Edge Team

    Changed Status to “Fixed”

  • Changed Status from “Fixed”

  • I hate to re-open this but on 16299.15, none of the fully qualified characters from “2660 FE0F ; fully-qualified # ♠️ spade suit” on down are still incorrect displaying as text not emoji. The text format keycap “002A 20E3 ; non-fully-qualified # *⃣ keycap: *” is also bad.

    Did you fix this for RS3 or RS4?

  • Microsoft Edge Team

    Changed Assigned To to “Steven K.”

  • Hi Richard,

    Never hesitate to re-open.  Appreciate the help verifying the emoji’s are working properly.

    I have attached a screenshot showing the spade section for the RS3 skip-ahead developer’s release.  Let me know if this does not look correct.  I am guessing all of the fixes did not make it into the insider fast release 16299.

    Also, I am attaching a recent developer’s build for the keycap section.  I see that there is possibly an issue here, I.e. assuming the font-family has a glif for the keycaps 0 - 9.  I will investigate why we aren’t seeing the fancy version like the 10 keycap for the fully qualified keycaps.

    Steve

  • Microsoft Edge Team

    Changed Assigned To to “wptcomptri@microsoft.com”

  • There is an Edge issue with the keycaps. I’ve attached a pic of Chrome 61 on RS3 16299.15 that gets these correct. Chrome 61 keys the suit emoji incorrect as well. What you see in your screenshot is the text presentation of the suit characters. I’ve attached a screenshot of the emoji presentation in WinWord 2016 on RS2 by setting the font explicitly to Segoe UI Emoji.

  • Thank you for the quick response and details.  I did verify the same by comparing with Chrome and have forwarded the expected representation.

    Steve

  • Microsoft Edge Team

    Changed Assigned To to “wptcomptri@microsoft.com”

You need to sign in to your Microsoft account to add a comment.

Sign in