TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Browsers handle emoji and punycode in different ways

1 点作者 xPaw大约 7 年前

1 comment

xPaw大约 7 年前
Was experimenting with emoji subdomain, and found that a lot of services and browsers all handle these inconsistently.<p>Firefox for example does not remove ZWJ from the emoji before converting it to punycode.<p>Microsoft Edge considers links that were manually converted to punycode invalid if they contain characters that Edge strips (like ZWJ and variation selector). Edge also returns raw emoji string in `location` API instead of punycode strings.<p>Safari does a whole lot of interesting things like displaying emoji instead of punycode in the address bar and use URI encoding in URLs.<p>Chrome seems to handle all of the cases the best.