Definitely a bug. Do you have pinned tabs also open in the tree?

Good idea. This should be doable without too much hackery. 

I think I'll play around with adding a small delay after the double-click is received before creating the new tab, and/or focusing the window shortly before creating the new tab ... perhaps some combination of these will get it working properly all the time.

Cool, thanks for the info. I think I probably just need to overhaul the whole pinned-tabs situation, which behave in a decidedly unique way vs regular tabs.

It is probably telling that it's a pinned tab that wound up like that.

Will research during next week's sprint, thanks for hanging in there.

Good gravy. Sidewise what you doing!!!

I'll do some thorough testing of various situations with pinned tabs in the next round of development. My guess is they are at the root of these problems you're seeing.

On my system, if you have it set to open the New Tab page when doing the double click, then the focus is set to the omnibox immediately after the New Tab page is opened. For the other options this doesn't happen on my machine.

Unfortunately Chrome doesn't provide any mechanism for extensions to focus the omnibox other than the aforementioned.

Thanks for the feedback. I see what you mean about moving regular tabs between pinned tabs - will look into this.

I don't know what the heck is going on with your normal tabs not being order-synced as expected -- I've tried to make this fail on my box in many different ways and it is always staying in sync here. I also can't seem to reproduce the "new tab -> quickly close" problem you mention.

If you don't have any pinned tabs open, does moving regular tabs around on the tabbar or in the tree do proper order sync for you?

Would you be willing to post some debug logs when you do the newtab->close thing? To do this, turn on the debugging option in Sidewise's options page, then on Chrome's extensions page turn on the Developer mode checkbox, find Sidewise in the list, click on background.html below it, switch to the Console tab, press the clear button at the bottom of that window, and finally perform the newtab->close operation, then copy everything that appears in the console and paste it in here.

Also, what version of Chrome are you using? Version 22.0.1229.94 m on WIndows 7 x64 here.

Thank you for your willingness to keep testing this stuff with me. These things are tough to diagnose when everything is working perfectly here and on other computers I have access to and I really appreciate your assistance.

Just released an update which I hope will fix the missing-tabs problem you reported. Hope you'll check it out!

-----

Sorry to hear the new version isn't working well for you. Unfortunately I haven't encountered the missing-tab problem you describe so I'm at a bit of a loss to help as of yet. One thing that may help is to just reload the extension -- I have a suspicion that that will restore those missing tabs to the tree and it should behave properly after that (hopefully).

As you say, Sidewise should control Chrome's tab order: that is the main new feature of the new version. Unfortunately it sounds like it isn't working right for you, but the intention was that the tab order should stay perfectly in sync between Chrome's tab bar horizontally and Sidewise's tree vertically. Currently Sidewise is set up to respect Chrome's tab ordering initially, and then if you move stuff around in the tree, reorder Chrome's tabbar accordingly (and vice versa).

I'll try to reproduce your situation of 2 pinned, 3 regular tabs today and see if I can somehow mimic the "missing tabs" issue you're having. My suspicion is if that wasn't happening, you would then be seeing the correct tab order synchronization that went into this new version.

I too wish there was some way to just hide Chrome's own tab bar altogether :) 

---

If you have any more information about what steps you took that resulted in the missing tab issue or suspicions please let me know. That is a show-stopper bug and though I can't seem to reproduce it here I'm very concerned about others running into it!