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.

Comments

This should really be two articles...

[Anonymous Coward]

Based on most Android and iOS articles I've read on /., this should really be two articles:

1. Apple ships support for Emoji ships, but it's rubbish and no one needs it anyway.
2. Google's amazing new Emoji for is almost ready to ship, revolutionising web browsing on OS X.

Re:This should really be two articles...

[stephanruby]

1. Apple ships support for Emoji ships, but it's rubbish and no one needs it anyway.
2. Google's amazing new Emoji for is almost ready to ship, revolutionising web browsing on OS X.

And Chrome Emoji support only works on OS X, whatever that means.

I assume that the unlucky Windows users and the unlucky Linux users will be left without the ability to express emotions on the internet anymore. That's the real tragedy here. The fact that all Windows and Linux users will be left emotionless if they can't afford to switch to OS X. As a Linux user, this makes me cry inside, but the best I can manage is this poor looking emoticon instead. :,-(

Oh damn you Linux! Damn you!! Why do you have to be so late at copying the big core features from everybody? If only Linux had come up with Emoji support a couple of years before everybody else, Desktop Linux would now be reaching 90% of the desktop market at the very least.

Who gives a fuck

[Anonymous Coward]

A) No one here uses emoji
B) No one here gives a fuck if you can enter emoji into a text field.
C) Why the fuck is the fact that you cant put emoji in a TEXT field considered a bug. Its a fucking TEXT field.

Re: Who gives a fuck

[tysonedwards]

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?

Re:Who gives a fuck

[Mr_Silver]

I consider then harmful.
I suspect Emoji are like those smileys with mustaches, beer steins, and birthday cakes that show up in skype chat. I hate that garbage. Many a time, I write a sentence that contains a parenhtesis, using grammar correctly, and then my message comes across as some random retarded shit sprinkled with smileys. I have a hard enough time avoiding typos, I don't really need the client mucking it up even worse.

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.