Your comments

I'm thinking this option should probably work like this:


  • Newly created tabs that are not a child of (opened from) some other tab get put at the top of the tree
  • Newly created tabs that ARE a child of some other tab get put into the tree nested under the existing parent (opener) tab, and pursuant to Chrome's own tab-ordering rules as far as whether they get put at the top, middle, or bottom of the parent tab's children

Does that sound right to you?

This is fixed in the upcoming release due out by end of month. Well, about as fixed as I can get it: when opening multiple bookmarks into a new window from the Bookmark Manager, Chrome actually claims that each successive bookmark is a child of (opened from) the preceding bookmark!

Fortunately there is enough information made available a bit later in the page-loading process to identify this case and retroactively flatten those pages. So immediately after opening those bookmarks, they will appear in the "nested under previous" way that they currently do, but a couple seconds later Sidewise will correct this.

#1: Unfortunately to my knowledge, there is no way to prevent Chrome from doing this. Sidewise creates a new Chrome window to put the sidebar in and as far as I can tell Chrome gives us no control over specifics such as taskbar button. The real fix is for Chrome team to implement a proper sidebar API that extensions can use.


#2: Completed, will be in next release due out by end of month.

Marking this as COMPLETED since #2 is done and we don't really have a good solution for #1. I'll be writing a FAQ page for Sidewise sometime soon and will include the information about TrayIt there just in case people want to go through that process to improve the existing behavior inasmuch as they can.

I'm currently working on making the tab order in the tree match Chrome's tab ordering, and keeping the two in sync at all times. I believe this will bring the behavior you want.

---

Sidewise will now do its best to mimic the tab-ordering that Chrome uses, as you describe. This will appear in the next release, due out by end of month.

Definitely planned, though it might not be the next version as I'm trying to freeze things for the next release which has been a while coming. Very probably would make it into the release after that if it doesn't appear in this next one.

---

OK, I just decided to knock this one out. This will appear in the next release which will be coming out sometime between now and the end of the month.

In addition to double-clicking on the empty space creating a new tab, you'll also be able to control (to a limited degree) which page is loaded into the new tab from the Sidewise options. Currently have implemented "New Tab page", "your homepage", "google.com", and "blank tab" options for this.

There is also a "Create new tab" button that appears at the right end of window rows in the page tree coming with the next release, which obeys this same setting.

Definitely planned, though it might not be the next version as I'm trying to freeze things for the next release which has been a while coming. Very probably would make it into the release after that if it doesn't appear in this next one.

---

OK, I just decided to knock this one out. This will appear in the next release which will be coming out sometime between now and the end of the month.

In addition to double-clicking on the empty space creating a new tab, you'll also be able to control (to a limited degree) which page is loaded into the new tab from the Sidewise options. Currently have implemented "New Tab page", "your homepage", "google.com", and "blank tab" options for this.

This is fixed for the next release, which should be coming out sometime between now and the end of the month.

Thanks for the report!

Definitely planned, though it might not be the next version as I'm trying to freeze things for the next release which has been a while coming. Very probably would make it into the release after that if it doesn't appear in this next one.

To clarify, does this accurately describe the situation on Mac?:

  • When the sidebar is not focused, clicking an item in the sidebar only focuses the sidebar; a second click is required to then actually select the item
  • When the sidebar is focused, a single click on an item immediately focuses it