Nolan Lawson @nolan@toot.cafe
Quiet public

I remember back in 2020 when I wrote emoji-picker-element, I was sure that using native emoji fonts was the way to go, and that I was skating toward where the puck was going. *Surely* we'd figure out all these font problems in no time, right?

And yet, things are actually worse now:

- Windows still won't show country flags
- Chromium still won't fix this for us issues.chromium.org/issues/407
- Safari still ties emoji to OS updates
- Firefox's bet on Twemoji went very south: bugzilla.mozilla.org/show_bug.

Chromium

issues.chromium.org

Nolan Lawson @nolan@toot.cafe
Quiet public

I'd like to say that this is something for standards to solve, but it's actually basically just browser bugs that the browsers themselves could fix but don't bother (likely because any web app that matters just ships their own bloated emojis-as-images anyway).

It's also unfortunately not the kind of thing you could fix with Web Plat Tests, because the Unicode Consortium mints new emojis every year, so the test is outdated as soon as you write it, and doesn't solve Safari version fragmentation.

0
0
0

If you have a fediverse account, you can quote this note from your own instance. Search https://toot.cafe/users/nolan/statuses/116037336943592087 on your instance and quote it. (Note that quoting is not supported in Mastodon.)