[WebView][M53] Emoji not supported when system language is Japanese
Reported by
seiyon.p...@gmail.com,
Oct 10 2016
|
|||||||
Issue descriptionSteps to reproduce the problem: 1. Go to Settings > Language > Select Japanese 2. Open any e-mail app using WebView 3. Open any e-mail which has emoticons What is the expected behavior? Emoticon should be displayed just as it is. What went wrong? WebView is displaying wrong emoticon. Did this work before? N/A Chrome version: 53.0.2785.143 Channel: stable OS Version: 7.0 Flash Version: Shockwave Flash 23.0 r0
,
Oct 10 2016
I got nothing.. Does this happen in chrome as well?
,
Oct 11 2016
,
Oct 12 2016
Looks like Emoji/text preference isn't working well. Note that this is device (default font) dependent. http://output.jsbin.com/dixuhom Samsung Galaxy S6 Edge: red, red, black Nexus 5x: black, black, black Sony SGP771: black, black, black The Unicode Emoji Data 4.0 says U+3297 is Emoji, so all these should be red. http://unicode.org/Public/emoji/4.0/emoji-data.txt
,
Oct 13 2016
kojii/drott: any ideas on a path forward or even just severity? - friendly on-duty bug triager
,
Oct 14 2016
,
Oct 14 2016
seiyon.park@gmail.com, is the behaviour identical on the browser and WebView?
,
Oct 14 2016
Note that in the original video report, the Emoji do appear, but in text presentation form. On which Android version was this tested? Could you provide the fonts.xml files from the devices you tested on, using # adb pull /system/etc/system_fonts.xml The Android code for retrieving the Emoji font relies on a special emoji locale to be put into the font family matching process, compare: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/platform/fonts/skia/FontCacheSkia.cpp?sq=package:chromium&dr=CSs&rcl=1476415104&l=88 Would be great if you could take a look as well, Koji. Perhaps we need some special handling here to make the Emoji locale the only one when we try to match for the Emoji font?
,
Oct 19 2016
It's verified that it's fixed on Dev version (M55). Thanks for you support on this isseu.
,
Oct 20 2016
If it's fixed on dev, would that have been related to your locale change on Android, Koji? (The one about sort of reverting to our previous workaround temporarily), compare https://bugs.chromium.org/p/chromium/issues/detail?id=652146#c15
,
Oct 21 2016
drott@: #9 sounds like so, but #4 looks strange, still in 56.0.2889.0 Canary today.
,
Oct 21 2016
Additional finding on #4: since we're using lang="und-Zsye", this should work only on N, where fonts.xml has:
<family lang="und-Zsye">
<font weight="400" style="normal">NotoColorEmoji.ttf</font>
</family>
Is this intentional?
The original reporter looks like he's using N.
Among the 3 devices in comment #4, only Nexus 5x is N, so disregard Galaxy and Sony.
On Nexus 5, if NotoColorEmoji.ttf has this character in black, it's safe to say the reverting order should have fixed this, now I'm wondering how I can confirm that.
,
Oct 21 2016
Screenshot of http://output.jsbin.com/dixuhom on my Nexus 5x, something looks wrong.
,
Sep 8 2017
Obsolete, works in more recent versions. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by rsgav...@chromium.org
, Oct 10 2016