The difference is the rendering engines for the browser windows.
We know Safari renders the character set differently than Chrome. But the Window UI elements (the tabs in Chrome) are okay. That's our biggest clue.
The window UI elements are likely (emphasis on likely, I may not be correct here) all being rendered by the OS. So they get the full OS-level emoji-expansion treatment.
But what happens inside a web browser window is all very browser dependent. The rendering engines are a big part of each browser's secret sauce.
Both Safari and Chrome use WebKit, but the similarities between the WebKit instances they use stop somewhere around the name of the engine. They're both forks from the main version and they're both heavily customized to improve the performance in ways that each browser development team thinks is meaningful for their end users.
@JasonSalaz found a great bug in the Chrome bug database that gives us the final clue that it's down to WebKit forks: http://code.google.com/p/chromium/issues/detail?id=90177 -- that bug is talking about the differences between the fork in Chrome and the mainline of WebKit from the open source project. There are rendering differences in the mainline that have yet to make it in to the version Chrome is using. And it looks like they intend to merge the changes in at some point.
Firefoxes is a shell scripts that will install all major versions of Firefox on OS X, and set up separate profiles so you can use them simultaneously. Currently it installs:
Firefox 2.0.0.20
Firefox 3.0.19
Firefox 3.5.9
Firefox 3.6.28
Firefox 4.0.1
Firefox 5.0.1
Firefox 6.0.1
Firefox 7.0.1
Firefox 8.0.1
Firefox 9.0.1
Firefox 10.0.2
Firefox 11.0
Firefox Beta
Firefox Aurora
Firefox Nightly
Firefox UX Nightly
You can set it up so it only installs the specific versions you want.
Optionally, the script can install Firebug for each version of Firefox too.
It will also set icons that contain the version number:
For Chrome/Chromium, install any version you want, change the app name from Chromium.app to e.g. Chromium 19.app for clarity, then disable auto-updates for that version.
Get VirtualBox and then run this ievms script. It will automatically download legal Windows images for testing purposes and set up virtual machines for every IE version you need.
Best Answer
Great couple of software to install to get a fully functional PiP feature in OSX from a Chrome browser :
Ah... and one last thing : this is free... ;)