Personally i don't think that this is something useful (have to many open tabs? simple click Close-Save All and start from scratch). I think that auto-closing process for windows might make them harder to delete from tree forever, as to decide delete or not it might require to see the content, and as so, to restore the window (which is more long in compare with bring to front already open). Also this will be constant source of garbage in the tree. Never actually understand this auto-closing extensions and how they might prevent tab clutter or be any useful, yet tabmemfree have 10 times more users than Tabs Outliner : ).

I think if somebody like this approach it is better to actually use separate extension for this. Then autoclosed items will be accumulated in a separate list, managed by separate extention, and the tree will be free of auto-produced garbage.

Yet it is not hard to do, and users in Chrome Web Store reviews asking for this feature. So if this feature will accumulate many votes (or donations ; ) it might be implemented.

Maybe really even as separate tree, specially for auto closed items, with an ability to restore them by dragging in the main tree. 

Personally i don't think that this is something useful (have to many open tabs? simple click Close-Save All and start from scratch). I think that auto-closing process for windows might make them harder to delete from tree forever, as to decide delete or not it might require to see the content, and as so, to restore the window (which is more long in compare with bring to front already open). Also this will be constant source of garbage in the tree. Never actually understand this auto-closing extensions and how they might prevent tab clutter or be any useful, yet tabmemfree have 10 times more users than Tabs Outliner : ).

I think if somebody like this approach it is better to actually use separate extension for this. Then autoclosed items will be accumulated in a separate list, managed by separate extention, and the tree will be free of auto-produced garbage.

Yet it is not hard to do, and users in Chrome Web Store reviews asking for this feature. So if this feature will accumulate many votes (or donations ; ) it might be implemented.

Maybe really even as separate tree, specially for auto closed items, with an ability to restore them by dragging in the main tree. 

Personally i don't think that this is something useful (have to many open tabs? simple click Close-Save All and start from scratch). I think that auto-closing process for windows might make them harder to delete from tree forever, as to decide delete or not it might require to see the content, and as so, to restore the window (which is more long in compare with bring to front already open). Also this will be constant source of garbage in the tree. Never actually understand this auto-closing extensions and how they might prevent tab clutter or be any useful, yet tabmemfree have 10 times more users than Tabs Outliner : ).

I think if somebody like this approach it is better to actually use separate extension for this. Then autoclosed items will be accumulated in a separate list, managed by separate extention, and the tree will be free of auto-produced garbage.

Yet it is not hard to do, and users in Chrome Web Store reviews asking for this feature. So if this feature will accumulate many votes it might be implemented.

Personally i don't think that this is something useful (have to many open tabs? simple click Close-Save All and start from scratch). I think that auto-closing process for windows might make them harder to delete from tree forever, as to decide delete or not it might require to see the content, and as so, to restore the window (which is more long in compare with bring to front already open). Also this will be constant source of garbage in the tree. Never actually understand this auto-closing extensions and how they might prevent tab clutter or be any useful.

I think if somebody like this approach it is better to actually use separate extension for this. Then autoclosed items will be accumulated in a separate list, managed by separate extention, and the tree will be free of auto-produced garbage.

Yet it is not hard to do, and users in Chrome Web Store reviews asking for this feature. So if this feature will accumulate many votes it might be implemented.

> I will try Alexander's suggestion :)

meantime is nothing to try, as TO does not support keyboard operations at a moment, so after activation you will be required to use mouse anyway. 

What i am talking about is that if TO window will be active (after activation by configured in Chrome extensions settings shortcut) they can accept shortcut not through Chrome, but directly. So it will be possible to close-save previously active window (from which) TO was activated using only keyboard.

Hmm... an idea, if this is all only about not to use mouse, what about shortcut to open or bring to front Tabs Outliner (can be configured as Alexander Phoenix suggest) and then one more shortcut (which will be processed by active TO) to save current active Chrome window (it is focused anyway when you activate extension button)?

Is this solve this problem? Full fledge keyboard support is planed in any case.... but maybe this shortcut need to do in a first place if this is so demanded.

really nice tip... yet to manually configure some additional extension to do this work (as i cannot do this through install) users first must become proficient with Tabs Outliner. And after that, the idea of saving some window through Chrome itself will be not so desired. Personally I have TO always visible. If not - it is only one click to open it for current window and to focus it in a first line - so by next click in TO you can save this current window. 

Is this really so needed feature to do something about or even to make so long conversation, I am really unsure. When Chrome will implement shortcuts i will add this.

Non an issue as if the item have the unload icon then it is represent the open Chrome item (tab of window). If accidentally deleted such items can be always restored from Chrome by the "Recent closed windows/tabs list".

The undo is planed anyway, and other features which can help resolve this issue even further, like the tree aware history, but this issue, as it is formulated, is actually not very critical - exactly this case - items with unload and delete icons actually have the undo possibility. 

So meantime i just trash this bug.

UPDATE: Or better leave it there with an answer.

Do you know that you can right click in Chrome tab strip (in any open Chrome window) and select "reopen closed tab" or "reopen closed window". 

Also any new empty tab in Chrome have in right bottom corner list of all recently closed tabs and windows.

Hope this help as temporary solution till there will be undo feature in Tabs Outliner.