Chrome Tabs doesnt activate the window that the tab is in
Hey,
Awesome actions btw!!
I was trying your Chrome tabs action and noticed that while it does select the specified tab in that window it doesn't actually activate or bring that window to the front which significantly reduces the usefulness of this action if you have more than one Chrome window.
Is there any way to add this functionality, similar to the Quicksilver Google Chrome plugin?
Tony
Oh, I hadn't realized. Yes, I'll fix that in the next day or two.
And done. Let me know if you have any trouble!
Hey, thx for fixing this.
Just tried it out and it's a lot better however i am still having some issues:
- A lot of times (~60%) the window with the tab i want is not in the foreground however all Chrome windows are activated and focused.
- LB doesnt hide after pressing return (similar to what spacebar does)
- sometimes when pressing spacebar to activate the tab i get an error (awesome feature btw)

Feature Requests :)
- can you display the tab url under the name. I have the setting to "Show all subtitles" disabled however i have seen LB still shows the subtitle depending on the content being displayed. ie when browsing bookmark history.
- Lastly, not sure if this is possible but is there any way to display the tabs in the order they were most recently used when first launching the action?
It's tricky. Chrome's applescript API won't let me raise the proper window into focus without swapping window indexes, and if I do that, unless you re-run the chrome tabs action anew everytime you use it, then selecting a new tab in the old results will mess things up.
can you display the tab url under the name
Sadly, unless you turn on subtitles the best I could do is append the url to the end of the title. The only actions that can override this are the ones Obdev built into launchbar (as far as I know).
is there any way to display the tabs in the order they were most recently used when first launching the action?
Sadly not. Chrome's applescript API is extremely limited.
I think the only way to implement your suggestions and provide a foolproof fix for the above is by creating an accompanying chrome extension to act as the middle man between the action and browser. I haven't done this before but I'll look into it.