Make emoji look good without explicit "Segoe UI Emoji" assignment

Fixed Issue #7900499

Details

Author
TJ V.
Created
Jun 15, 2016
Privacy
This issue is public.
Reports
Reported by 8 people

Sign in to watch or report this issue.

Steps to reproduce

If I render an emoji on the web I expect it to look good, but currently in Edge my emoji render in black and white and are boring. I’ll insert a few here so you can see for yourself.

😀🎉🔑🚀

To make this emoji look good in Edge I have to explicitly set the font-family of the emoji’s containing HTML element to "Segoe UI Emoji", which is unintuitive, and a nuisance.

This may be a Windows thing instead of an Edge thing. On OS X (or macOS, or whatever) zero browsers require an explicit font-family assignment, but on Windows I get the behavior in Chrome that I do in Edge. (I will say Firefox on Windows is doing something because my emoji look far better there.)

I wrote up a blog post that gives specific screenshots that might be more clear than the description in this ticket: https://www.tjvantoll.com/2016/06/15/emoji-on-windows/.

My request is to have Edge automatically detect the unicode for emoji and automatically assign the “Segoe UI Emoji” font family.

Thanks!

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Brad E.”

      Changed Assigned To to “Christian F.”

    • Looks like Chrome 53 updated to include color Emoji by default on Win 10 while Edge is still black and white. Gotta get this fixed & stop letting Chrome beat you on your own turf!

    • Still not fixed in 1493.187

    • Not fixed in 15.15002.

    • This is fixed in Edge 15.15010.1002. Note that IE11 still has the black-and-white emoji, though.

      Here’s a small repro to demonstrate: http://bl.ocks.org/nolanlawson/raw/46314a8558e984b3fed4695c99f46290/ . On that page, both rows of emoji should be full-color. 

    • Microsoft Edge Team

      Changed Status to “Fixed”

    • Hello,

      Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 15063 and is available in our latest Insider Preview build.

      Best Wishes,
      The MS Edge Team

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

    Sign in