Chrome For OS X Catches Up With Safari's Emoji Support
According to The Next Web, Emoji support has landed in the latest developer builds of Chrome for OS X, meaning that emoji can be seen on websites and be entered into text fields for the first time without issues. ... Users on Safari on OS X could already see emoji on the Web without issue, since Apple built that in. The bug in Chrome was fixed on December 11, which went into testing on Chrome’s Canary track recently. From there, we can expect it to move to the consumer version of Chrome in coming weeks.
While it is absolutely the case that emoji has no place in certain text fields, as a web browser it is Chrome's responsibility to handle all valid and compliant UTF-8 symbols, including emoji symbols, within the application. Emoji are not some imaginary pseudo-symbol type or image format sent in-line. Where the symbol is seen, an image from a font will be displayed instead of a conventional character. As such, is it really that different than needing to support Cyrillic characters in text fields?
Thirty four characters live here.
That's not the fault of Emoji, that is the fault of the client replacing things like ":)" and ";P" with pictures in order to simulate Emjoi.
As bizarre as it sounds, you actually want to be embracing the support of Emoji! This is because all the searching and replacing logic (which, as you rightly pointed out, tends to make unwanted changes to your text) is now redundant and can be removed by the developers.
The net result is that people can still insert smileys with moustaches, beer steins, and birthday cakes and you can still type grammatically correct messages (or code) without fear of them being replaced with pictures. A win for everyone.
Avantslash - View Slashdot cleanly on your mobile phone.