Hmm, works for me.

"Restore saved windows in the original position and size."

must be checked. Also to save the position and size you must save-close window by green x in TO. And this will start to work only for newly saved windows - not for a saved windows you already have in tree.

If it is not work....

well, that is interesting then.

But i just test it in different scenarios - seems work ok...

It is already implemented for a long time, yet without cascade, see the options (must be enabled to work, off by default). Just forget to update the bug.

The TO is even not trying to be always on screen as you might notice... so it is expected that most of the time you will actually use the original tab strip.

And in some next release i even plan to make the non-autoscroll the default... that was a mistake. Personally i disabled it long ago.

Also i think it worth to note that this tool is not aimed to be the Chrome tabs strip replacement, as for example the Sidewise do. 

This is more an organizer for saved tabs then something that what was the original TreeStyleTabs (in Firefox) or the Sidewise. 

So aims is very different, and a target audience also (and that was also one of the reason i drop and cut the original Tree Style Tabs Outliner name, despite the fact that this might lead to some easy traffic - note that TO was released before the Sidewise, so might easily be the first (working) TST for Chrome - yet I decide not to take this name to not mislead the people). This is also why i not try to pretend that this is a sidebar, and many other decisions (like doubleclick to restore by default (can be switched to one click, but not recomended) and so on).

So if you like such Sidewise features like middle click to close, or something that they do with mouse wheel (never actually try) and so on - i think it is better idea to stick with Sidewise, very unlikely i will do all of this  - have a huge list of other more important features to do.

Yet for example better search there will be of course (and it will be much better...). 

Middle click already has some very useful behavior which is actually used as for me as for many other users. And even mentioned in quick start guide, because of its usefulness.

It's open the tab in last focused window without restoring it in place, sometimes this is very handy.

Yet actually i cannot remember that i was used this for already open tabs. But this is an additional option and additional documentation paragraph and a little more to learn and read for every new user, and additional feature to support and test for me.

All of this ok if there is really many who need this. But I hear such request the first time. Will see if they get some up-votes.

Problem is detected and fix/workaround will be released soon (i hope - today). This is actually a Chrome v26  bug, Chrome extensions API start send inconsistent events in some cases. 

Yet of course it is impractical to wait till the Chrome team will fix this (if they will be bothered at all, some serious bugs that i report to them was ignored, even despite they are regressions). So i will release a workaround on my own.

UPDATE Fixed in v0.4.55 - wait till your copy will be update or force update by entering the developer mode in the extensions list and pressing "Update Extensions Now" button.

Problem is detected and fix/workaround will be released soon (i hope - today). This is actually a Chrome v26  bug, Chrome extensions API start send inconsistent events in some cases. 

Yet of course it is impractical to wait till the Chrome team will fix this (if they will be bothered at all, some serious bugs that i report to them was ignored, even despite they are regressions). So i will release a workaround on my own.

UPDATE Fixed in v0.4.55 - wait till your copy will be update or force update by entering the developer mode in extensions list and pressing "Update Extensions Now" button.

Problem is detected and fix/workaround will be released soon (i hope - today). This is actually a Chrome v26  bug, Chrome extensions API start send inconsistent events in some cases. 

Yet of course it is impractical to wait till the Chrome team will fix this (if they will be bothered at all, some serious bugs that i report to them was ignored, even despite they are regressions). So i will release a workaround on my own.

It is look like some new bug in Chrome v26. I see that the users of some other similar extensions now start to report very similar problems in theirs support groups.

The exact case of how this happens is still unknown for me, yet i saw this problem several times already . 

Closing and open TO window does nothing in terms of recreating the tree. You need to disable->enable it in Settings\Extensions, or on this page chrome://extensions (but don' press the trash icon, this will uninstall and delete all data) if you want to do so.