Edge does not support Unicode variation selectors (U+FE0E for symbols, U+FE0F for emoji)

Duplicate Issue #13515601 • See Issue #11635143

Open new issue

Browse all tracked issues

Details

Author
Joshua F.
Created
Aug 30, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Standard affected
FAQ - Variation Sequences

Duplicates
See progress on Bug #11635143
Reports
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

For Unicode glyphs with multiple variations, Edge is the only major browser to not support choosing the variation to display using Unicode variation selectors. The 2 most common selectors are U+FE0E for symbols, and U+FE0F for emoji.

http://unicode.org/faq/vs.html

Edge and IE only support symbol/emoji selection by changing font-family to Segoe UI Symbol/Emoji, and currently defaults glyphs to the emoji variant, which can look out of place when glyphs are used to style UI elements.

Open this codepen in different browsers to see compatibility differences.

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Steven K. Aug 30, 2017 2017-08-30T04:57:07.37Z

      Changed Assigned To to “Steven K.”

    • Steven K. Sep 1, 2017 2017-09-01T05:04:33.617Z Microsoft Edge Team

      Hi Joshua,

      What version of Windows 10 are you using?  Win+S and then type ‘winver’ and hit enter.

      Steve

    • Joshua F. Sep 1, 2017 2017-09-01T05:07:57.12Z

      Version 1703 (OS Build 15063.540)

    • Microsoft Edge Team

      Steven K. Sep 1, 2017 2017-09-01T07:25:27.053Z

      Changed Status to “Duplicate”

    • Anonymous Sep 1, 2017 2017-09-01T07:25:54.243Z Microsoft Edge Team

      This bug has marked as duplicate. Please follow the parent issue to get new updates.

    • Steven K. Sep 1, 2017 2017-09-01T07:34:49.853Z Microsoft Edge Team

      Thanks for the quick response. 

      This is actually a duplicate of another bug report.  While investing that bug report, I realized the variation selectors were not being used.  So at first that report may not look like a duplicate, but it is in fact the same issue.

      You can follow that bug report with this link:

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

      Appreciate the support and the very nice repro.  :)

      The MS Edge Team

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

    Sign in