Steps to reproduce

View http://www.unicode.org/Public/emoji/5.0/emoji-zwj-sequences.txt in Edge 41.16251.0.0 on RS3 16251.0 insider preview. Most of the gendered roles, all starting from "Emoji ZWJ Sequence: Gendered Role", are displayed incorrectly without the gender modifier being applied. These same emoji display correctly in Windows 10 Mail, OneNote (store app), and OneNote 2016. I didn’t try other apps with the exception of Notepad. Even Notepad displays these correctly except when there are skin tone modifiers.

I’ve attached a PNG of the end of the file that shows the gender selector displayed separately from the base emoji. I also attached a PDF of the entire file. Both are from Edge 41.16251.0.0 on RS3 16251.0 insider preview.

The PDF demonstrates a separate issue where the alignment in the print out is nothing like what is displayed on screen. I’ll report this separately since I do not think it is emoji related.

Some yes. What I see is that the gendered with object variants work. These are those that use joining a man (U+1F468) or woman (U+1F469) emoji with a plant emoji resulting in a male or female farmer emoji. The ones that do not work, and there are many more of these, are those that join an existing or new emoji that may have a default gender with the gender selectors U+2640 and U+2642.

How long to the fixes that were made for the presentation selectors, text or emoji, RI’s to main and makes it to an RS3 insider preview?

I should point out that the emoji-test.txt examples include the use of the U+FE0F emoji presentation selector but not the U+FE0E text presentation selector. Edge’s lack of support for these was covered by a different bug I filed. That is supposedly fixed internally. This document does include a number of emoji which are displayed correctly with the FE0F selector but as two different emoji without the selector which is a bug which I don’t know is fixed or not.

If you can, please share your findings and issues with other teams. There are other Microsoft and even Win10 RS3 components that don’t handle emoji correctly. You can open or past the text from http://www.unicode.org/Public/emoji/5.0/emoji-test.txt into WordPad (RichEdit) or Word 2016 and see that they get most wrong even if the font is set to Segoe UI Emoji. Note that if you load instead of copy and paste, the file lacks a UTF-8 BOM so will not be loaded correctly by either. If you add a UTF-8 BOM, Word 2016 Build 1708 8417.1000 Office Insider Fast does much better but still fails more than it gets it right.

Modern apps are also bad. OneNote and Mail, both on RS3 preview, do poorly. I don’t know if either uses Edge for rendering. Sticky Notes is another I tried that gets much wrong.

Probably. That bug lists only a single emoji while here I provided the test file for all of ZWJ gendered sequences, albeit with an explicit emoji presentation selector.

The emoji-test.txt file I mentioned in the comments includes the explicit and implicit emoji presentation but not the text presentation. Another bug I filed reported issues with explicit and implicit text presentation. That latter issue is also fixed but not yet flighted.

Did you note that the other bug also discloses a bug in the address bar control? The address bar edit displays the emoji in that bug correctly but the suggestions dropdown does not.

All gender sequences in emoji-zwj-sequences.tx are all forming as expected.

Emoji presenation respects correct selector. Although, if character is covered by explicitly specified font, preference is given to glyph from this font rather than any fallback font based on presentation selector.

But I am on a bit newer build than 16257, so some fixes may not be in public preview yet.

I should have made it clear that couple/kiss, rainbow flag, and eye in speech bubble emojis are a regression from 15063. The gendered people bouncing ball, lifting weights, and golfing emoji are broken in both 15063 and 16281.

Suggesting a root cause

Help make the web just work! Identifying a root cause helps us resolve issues more quickly. If you have a theory for the root cause or have identified and reduced a reproducible bug, include a description and any relevant code or URLs in your comment and mark it as a root cause suggestion. Our engineers will take a look and update the bug with the results of our investigation.