Issue metadata
Sign in to add a comment
|
Blink is unable segment correctly in order to render one of Microsoft easter egg Color Emoji, Ninja Cat Flying, "🐱🏍" |
||||||||||||||||||||||||
Issue descriptionChrome Version: 56 OS: Win10 What steps will reproduce the problem? 🐱🏍 What is the expected result? Like Firefox and Chrome UI What happens instead? It is rendered with two Character instead. Microsoft has a number of MS specific Emojis called Ninja Cat on Windows. http://blog.emojipedia.org/ninja-cat-the-windows-only-emoji/ They all working on Chrome except this one. I see this an minor polish bug (if it doesn't reveal a bigger issue) and I don't know the very detail if this worth to be fixed (it is from a different code page, but Firefox handles it well AFAICS) but I thought it worth to have a bug anyway.
,
Dec 13 2016
,
Dec 13 2016
Hmmm, now I think this is another instance of Issue 617631, sorry if my initial speculation misled you.
,
Dec 13 2016
,
Jan 11 2017
Well, Emoji 5.0beta data does not list any Emoji ZWJ sequences with U+1F431 (🐱). So, it's not a data issue. See http://www.unicode.org/Public/emoji/5.0/emoji-zwj-sequences.txt. This issue is what to do when coming across a sequence NOT enumerated in the emoji data BUT supported by an emoji font. (e.g. <U+1F431, U+200D, U+1F3CD> ; I think sequences like the above should be treated as a unit - don't we do that already? - and a single font supporting them should be used). ebrahim@, your sample text does NOT have U+200D (ZWJ) between U+1F431 and U+1F3CD. So, it's expected that they're not combined into a single glyph. I don't have Win 10 around. Can you try again with ZWJ put between two characters?
,
Jan 11 2017
,
Jan 12 2017
Doesn't work with ZWJ either, this bug is obscure, MS specific, and can be closed with WAI/WONTFIX, but the main point is why 🏍 is not rendered with color emoji at all which is covered by Issue 617631 among many several others. Not necessarily data issue, it could be a segmentation issue like https://codereview.chromium.org/2473863003/
,
Jan 12 2017
,
Jan 13 2017
> Doesn't work with ZWJ either, Hmm.... Regardless of whatever is in Emoji database, <C1, ZWJ, C2> had better be treated as a single grapheme and passed to a font/shaping engine down the stream as such. Apparently, that's not happening somehow. > the main point is why 🏍 is not rendered with color emoji at all That's indeed odd. If it's a text iteration/segmentation issue with non-BMP characters, it'd not be just those two characters but almost all Emoji characters (because they're in Plane 1) would break. > Issue 617631 bug 617631 cannot be responsible for that, either because ICU 58.1 (used by Blink) already has Emoji 4.0 (the latest release) which treats 🏍 as Emoji by default.
,
Jan 14 2017
> bug 617631 cannot be responsible for that, Title of that got changed later, please open the testcase itself on a Windows 10 machine, that testcase contains 🏍 also.
,
Sep 16 2017
Friendly ping
,
May 31 2018
Apparently this no longer is available on Windows but 617631 can be fixed. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by e...@chromium.org
, Dec 12 2016