Comment 26 for bug 488958

It's years later. Let's catch up. :-) I'm using Trusty beta, and chrome 33, and just today I started using Docky because of issues with not being able to move Unity's Launcher and multiple monitors. It's all looking very promising...

I use the TweetDeck webapp. I had already done the thing to create a shortcut in the menu (which puts a .desktop file in ~/.local/share/applications) In Launcher this behaves as you would expect, like a separate application. You can launch it from Dash, lock it to the launcher, it opens a separate window and the launcher icon has a little arrow next to *it* when it's running, and not an extra one on the Chrome icon. etc. etc. In other words, entirely as you'd want, and like it's a standalone application.

With Docky, you have to find the .desktop file and drag it to Docky to add it. That works. But when you click on it, the window opens properly (ie: without browser furniture, tab/tool/bookmark bars etc.) but it's the Chrome icon in Docky that gains an extra light. And other behaviour that basically means, it's still not thinking of it as a separate application but just working as a dumb launcher.

That Chromium bug linked above is marked as Fixed (as of April 2011, a little after the most recent comment here), and as noted, it works in Launcher. ;-) As far as I can scan the fix seems to relate to BAMF, and that was mentioned earlier here. Is Docky not using BAMF yet as of 2.2? It seemed implied to be work in progress 3.5 years ago above. :-}