- From: Gary Pendergast <notifications@github.com>
- Date: Thu, 21 Dec 2017 04:20:43 +0000 (UTC)
- To: w3c/permissions <permissions@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 21 December 2017 04:21:06 UTC
I'm the WordPress maintainer mentioned in the OP. 🙂 We've found over time that the canvas render method is the only reliable way to determine if the current browser/OS will render emoji correctly. There's some relevant discussion on [one of our tickets](https://core.trac.wordpress.org/ticket/42428). I certainly appreciate that the privacy issues are more complex than simply providing a flag to determine if the current browser will allow the canvas image data or not. If something resembling that flag were available, however, we'd definitely want to include a check for it on all WordPress sites. An alternative option for us, which is wildly out of scope for this issue (but may be of interest), is if the browser was able to determine if it supports rendering current emoji sets, we'd be more than happy to use that information instead. We've found that we can split emoji support into testing for whether we can render all flags, and whether we can render other emoji from the latest spec. Currently, we test the [UN](https://emojipedia.org/flag-for-united-nations/) and [England](https://emojipedia.org/flag-for-england/) flags, and the [Male Fairy](https://emojipedia.org/man-fairy/) emoji. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/permissions/issues/165#issuecomment-353254684
Received on Thursday, 21 December 2017 04:21:06 UTC