Some new emoji can't display and show up as a square. i.e. http://emojipedia.org/first-place-medal/ <- this one can display in Edge, Opera and even in notepad.
Do they show up in Chrome?
@enlight Yes. It's show up properly both in address bar and in page content.
@iNViTiON Are you using Chrome stable channel?
@zcbenz Yes. Version 53.0.2785.116 m
Version 53.0.2785.116 m
I'm having trouble reproducing this, I see that example emoji in both Electron and Chrome on Windows 10 1607.
@iNViTiON what specific Windows 10 version are you on? And can you include a screenshot of what you are seeing?
@kevinsawicki It look like the one appear on visual studio code. It also like this on my app too.
@iNViTiON I don't think Visual Studio Code is using Electron 1.4 yet, can you try running npm install -g email@example.com and then run electron http://emojipedia.org/first-place-medal and see if they show up there?
npm install -g firstname.lastname@example.org
@kevinsawicki I change package.json start script from "electron ." to "electron http://emojipedia.org/first-place-medal" to make sure that it the same version as I got with my app and it display correctly. But when I change back to "electron ." to run my app and it still show as square.
Here was it show on my app.
And it also can't type in Electron even it can display correctly in site content?
@iNViTiON can you provide a minimal app that demonstrates this issue for you to help us reproduce this?
@kevinsawicki OK. I fork the quick start to demonstrate this here. -> https://github.com/iNViTiON/electron-quick-start
It should look like this.
Thanks for the example, was able to reproduce, it is deciding to use Arial for those emojis instead of Segoe UI Emoji for some reason.
Segoe UI Emoji
If you explicitly set the font-family in CSS to Segoe UI Emoji for those elements, they do render correctly in Electron.
@kevinsawicki Thank for quick fix.
Found the related Chromium issue that added support for this, https://bugs.chromium.org/p/chromium/issues/detail?id=620419
An upstream Chromium fix for this has been opened at https://codereview.chromium.org/2387373003/
Update libchromiumcontent for #7334