I would like to have the option to have links in new tabs opened in the foreground, not the background as currently happens.
I would like to have the option to have links in new tabs opened in the foreground, not the background as currently happens.
To open a new tab in foreground you only have to press CTRL+SHIFT and then click with the left mouse button the link you want to open in a new tab.
This has been brought up before. I also want the auto-select new tab which I have on firefox. Also having searchbar with generating new tab and auto-selecting it.
Not all of us want keyboard options... I always have my coffee,soda,pizza,cig,etc in my left hand while I surf and wake up reading my sites. Sorry but for me anyways this is a deal breaker for me.
That and ad-block. When those come to chrome then I will come to using chrome as my main browser and not until then. I hope the best for chrome and hope it does become my main browser.
I've been using Chromium Nightly Builds and this is the only thing I've found broken. Control Shift Left Click opens in background tab. So does Control Click.
I've gone back to the version I used previously. Same thing. I guess I just haven't noticed when the fault appeared. Kind of annoying because I use a macro to send Control Shift Click when I Control Click and now I still can't get stuff to open in foreground tab. It's broken whether the macro program is running or not, so it's not the macro. The only way I've found to open in a new tab in foreground is in Speed Dial to right click and click on Open. Then it opens in the foreground, but that only works for dials. Regular links or bookmarks it opens in a background tab no matter what.
Looks like the only way I can do it is to drag the link to the tab bar with the mouse. I just installed current nightly and the tab click behavior is still broken. If I use Tabs To Foreground extension then I can't open in background. One would think this basic function should be easily enabled for both cases with an option. Seems like developers want to force users to do it their way.
edit: btw for anyone using the nightlies, I haven't tracked the build where the bug first appeared, but using 63747 works normally. Guess I'll stay with that until the fix is in, so to speak.![]()
Last edited by MilesAhead; 11-09-2010 at 02:17 PM.