4 ms·

Not sure if the issue is with Chrome or my local config generally (bog standard Windows, nothing fancy), but the us-flag example doesn't render as intended. It

Not sure if the issue is with Chrome or my local config generally (bog standard Windows, nothing fancy), but the us-flag example doesn't render as intended. It shows as "US" with the components in the next step being "U" and "S" (not the ASCII characters U & S, the encoding is as intended but those characters are being given in place of the intended). Displays as I assume intended in Firefox on the same machine: American flag emoji then when broken down in the next step U-in-a-box & S-in-a-box. The other examples seem fine in Chrome. Take care when using relatively new additions to the Unicode emoji-set, test to make sure your intentions are correctly displayed in all the brower's you might expect your audience to be using.

SethMLarson 5y ago
Yeah, there's not much I can do there unfortunately (since I'm using SVG with the actual U and S emojis to show the flag). I can't comment on whether it's your config or not, but I've tested the SVGs on iOS and Firefox/Chrome on desktop to make sure they rendered nicely for most people. Sorry you aren't getting a great experience there. Here's how it's rendering for me on Firefox: https://pasteboard.co/rjLtqANVQUIJ.png https://pasteboard.co/rjLtqANVQUIJ.png
- xurukefi 5y ago
  For me it also renders like this on Chrome/Windows: https://i.imgur.com/HCJTpfA.png https://i.imgur.com/HCJTpfA.png Really nice diagrams nevertheless
- dspillett 5y ago
  Yep, that is what I get in FF to. And Chrome on Android, though with a rendering difference on the not-plain-ol'-U and not-plain-ol'-S (in both cases, blue letters rather than white with a blue background).
andylynch 5y ago
They aren't new (2010) - this is a Windows thing - speculation is it's a policy decision to avoid awkward conversations with various governments (presumably large customers) about TW , PS and others -- see long discussion here for instance https://answers.microsoft.com/en-us/windows/forum/all/flag-emoji/85b163bc-786a-4918-9042-763ccf4b6c05 https://answers.microsoft.com/en-us/windows/forum/all/flag-e...

SethMLarson 5y ago

Yeah, there's not much I can do there unfortunately (since I'm using SVG with the actual U and S emojis to show the flag). I can't comment on whether it's your config or not, but I've tested the SVGs on iOS and Firefox/Chrome on desktop to make sure they rendered nicely for most people. Sorry you aren't getting a great experience there. Here's how it's rendering for me on Firefox: https://pasteboard.co/rjLtqANVQUIJ.png https://pasteboard.co/rjLtqANVQUIJ.png

xurukefi 5y ago
For me it also renders like this on Chrome/Windows: https://i.imgur.com/HCJTpfA.png https://i.imgur.com/HCJTpfA.png Really nice diagrams nevertheless
dspillett 5y ago
Yep, that is what I get in FF to. And Chrome on Android, though with a rendering difference on the not-plain-ol'-U and not-plain-ol'-S (in both cases, blue letters rather than white with a blue background).

andylynch 5y ago

They aren't new (2010) - this is a Windows thing - speculation is it's a policy decision to avoid awkward conversations with various governments (presumably large customers) about TW , PS and others -- see long discussion here for instance https://answers.microsoft.com/en-us/windows/forum/all/flag-emoji/85b163bc-786a-4918-9042-763ccf4b6c05 https://answers.microsoft.com/en-us/windows/forum/all/flag-e...