Tabs Outliner will be developed in this direction, to become a full feature task and project manager.

But the fake(meantime) tags is something i really use and it's actually very useful concept. Often using them in Google Docs titles - then the search through the tree will also find them easily - as they become a part of tab title.

> but no way I can figure to "refer" to my tree

I found that using tags (meantime fake, real support is planed) is an excellent way to link data between different programs and even between electronic data and notes on a plain paper.

I just mark something with some tag, for example
#project-x  #feature-y #task-z
and then using this tag in paper notes and in x-mind and in Google Docs - inside documents, and then, by seeing it i know that if something refer to this tag then the TO tree contain some more information near the note with such tag - so i just use search to find this "some more".

So basically a solution is not to use a full task name or long title but a short tag. Then it's possible to easily use it as in paper notes, as in TO tree, as on Post-It stickers.

The cool thing about this as it is always easily to add more information to some topic this way. Without even searching the place where to put it. Just by adding already existed tag to it. It's also handle moves and copy operation excellent - something that is very complex to accomplish with URL scheme. 

This works much better for me than using the links. I really connect this way information through many different programs.

But the links is also planed, as to nodes, as to tags (then TO will perform an automatic search before displaying the page, obviously for this needed a server side)

> Closing Chrome and reopening Chrome has no effect.
Also please try to exit Chrome completely
Through the Exit menu item in its main menu.
Often just closing the Chrome does not completely restart it.

Yes, reinstalling will clear the tree. 
Note that you can save a read only version of the tree in HTML file, through Ctrl-S (expand all nodes before this). From such file is possible to drag hierarchies back to main view.

Interesting issue. I cannot reproduce this. And of course if this will be a common problem than there will be literary hundreds of such reviews and emails.

The log file unlikely will help.

Through you might try to open the console of Tabs Outliner view. Maybe it contains some errors.

Try to drag items (to produce fail scenario)
Right click anywhere, select "Inspect element"
Select console (last menu item) in the window which will open.
Copy there its content.
Maybe it contains some clues.

Also please try to remember what event happens with Chrome just before this problem. Something that might look relevant.

An alarming issue.
Please clarify.
What OS do you use, what Chrome/Chromium version?
There is no such feature to lock the dragging.
And i cannot reproduce this issue myself.

Does the Chrome restart helps?

Was a problem in Chrome itself.

As for now the problem is fixed in the latest Chrome STABLE.

PLEASE UPGRADE YOUR CHROME to version 32.0.1700.102 (through About dialog)

UPDATE
As for now the problem is fixed in the latest Chrome STABLE

PLEASE UPGRADE YOUR CHROME to version 32.0.1700.102 (through About dialog)

------------------------------------------------------
Seems all extensions that render self in panel window is affected.
tree still can be scrolled by scroll bar if opened in a regular window, through Clone button. Or by arrows and mouse wheel.

Seems there is no fix in Chrome is expected very soon, as all current Dev builds have this bug, and so even if they will be fixed by Chrome team tomorrow it come to Stable build only in several months.

Meantime maybe will try to find some workaround in extension itself.

For anyone who reading this - please star this Chrome issue:
https://code.google.com/p/chromium/issues/detail?i...

UPDATE: Problem affect only Windows 7. Also the bug is already marked as fixed and is really fixed now in Dev and Canary Chrome builds. But it's a question when it finally will arrive in the Stable chanell.

UPDATE
As for now the problem is fixed in the latest Chrome STABLE

PLEASE UPGRADE YOUR CHROME to version 32.0.1700.102 (through About dialog)

------------------------------------------------------
Seems all extensions that render self in panel window is affected.
tree still can be scrolled by scroll bar if opened in a regular window, through Clone button. Or by arrows and mouse wheel.

Seems there is no fix in Chrome is expected very soon, as all current Dev builds have this bug, and so even if they will be fixed by Chrome team tomorrow it come to Stable build only in several months.

Meantime maybe will try to find some workaround in extension itself.

For anyone who reading this - please star this Chrome issue:
https://code.google.com/p/chromium/issues/detail?i...

UPDATE: Problem affect only Windows 7. Also the bug is already marked as fixed and is really fixed now in Dev and Canary Chrome builds. But it's a question when it finally will arrive in the Stable chanell.

Yes, group is a complete equivalent to a named window. Except it is created as not active window - which is very handy in many cases.

Windows do not disappear on close in next cases:

• They have custom title
• Or they have a note somewhere inside (or other node that is not a open tab)
• Or, if they placed above the root level, inside some other node.
  

TO, at least for me, is not replace anything (except maybe a windows taskbar to select Chrome windows). It's a very useful thing on its own, and i very often use the original Chrome tabs strip directly - to switch in one click, to move tabs between windows, to multiselect tabs.

Inside TO i very often add notes and tags to things (tags meantime is just a text, like this - #project-x #to-read #to-learn #must-read #to-print ..., without even auto-complete or anything, but i hope i implement a full support for this soon)