Only activate the chrome window that contains the tab that is revealed

[sinewave]

Hey,

Now that i have switched back over to QS from Alfred i find i am using this plugin a lot especially with the newly added search by url (TKU!).

A minor annoyance i wanted to ask you about is if it would be possible to only activate the chrome window that contains the url tab that is being revealed?

At work i have three monitors and usually have different apps setup on each window. My issue is that when i reveal a tab it activates all the chrome windows instead of just the one containing the tab. This is annoying because i then have to reactivate/hide the other chrome windows or windows i was working on before.

Not sure if this is an easy fix but would definitely make using this plugin more enjoyable.

And thx again for creating this plugin, it is really awesome!!!

[ndreas]

Another great idea, and I think it might be doable. I'll take a look at it.

[ndreas]

Unfortunately, my guess was wrong. After doing some searching and testing, it seems it's not possible to activate a single Chrome window instead of the entire application. Too bad, I really liked the idea.

[sinewave]

Ok, thx for trying.

Although i have used an app called Optimal Layout in the past as a window manager. It also happens to have some functionality built in to allow you to search for a chrome tab and reveal it. I dont use the app as much because it has some issues and i have been using ur plugin :)

The reason i mention this app is because it is able to activate only the window with the tab you selected. Not sure how he is doing this or if its because this is a qs plugin that doesnt have access to the same settings?

Anyway, just thought i would mention it.

[ndreas]

Seems I might have been a bit hasty. Information regarding this is a bit hard to find.

I did a bit more digging, and found a way to only focus the frontmost window of an app, and I got it working. But, I can't seem to get Chrome to set which window should be the frontmost. I'll work on it and see what I can come up with.

[sinewave]

Ok, sounds good.

Look forward to seeing what you discover :)

FYI, i also noticed that not only does it activate all chrome windows but it also "focuses" the window that was last active which is just as much of an issue imo because the tab you just revealed doesnt actually have focus and will not respond to keyboard events, etc...

[ndreas]

Yes I saw that almost immediately when I started testing, definitely a bug. Unfortunately, this seems to be an issue with the Scripting Bridge interface used to talk to Chrome. I'll see what I can do to work around it.