OK. It sounds like a pretty rare problem, and I have not been able to reproduce it yet, so I'll keep an eye on it and if you happen to reproduce it again let me know. 

Cool idea.

• Have you used the "reorder panes" function in the options page before?
• Once the Notepad pane actually *does* appear correctly, does switching between Pages and Notepad after that point work correctly no matter how many times you do it?

I will investigate what is possible without going through an external server to share cross-session data. My suspicion is that Chrome just treats each Chrome user session as a completely separate running Chrome instance, with no knowledge of the other user-instances that may be running.

Using an outside server would introduce latency and connectivity issues which could complicate the solution considerably.

One potential avenue that is cross-platform and Chrome-specific is using PPAPI to create a message pipe between all Chrome user-instances on which the PPAPI "helper" is installed. I'm not sure if PPAPI is ready for primetime yet though.

I will investigate what is possible without going through an external server to share cross-session data. My suspicion is that Chrome just treats each user as a completely separate Chrome instance, with no knowledge of the other user-instances that may be running.

Using an outside server would introduce latency and connectivity issues which could complicate the solution considerably.

One potential avenue that is cross-platform and Chrome-specific is using PPAPI to create a message pipe between all Chrome user-instances on which the PPAPI "helper" is installed. I'm not sure if PPAPI is ready for primetime yet though.

AHK could handle such communication, but only on Windows. 

I tried doing that initially, but unfortunately Chrome has a problem where selecting or "highlighting" tabs on the tab bar causes Chrome to also switch focus to each of the tabs you highlight in turn. Which means as you expand your selection in the tree, Chrome is busily tab-switching to each item in your selection. Imagine shift-selecting 50 tabs in the tree ... you see the problem.

It did work in that you wound up with synchronized selections between Chrome and Sidewise, but I had to remove this functionality due to the tab-switching issue.

If you'd like to see Chrome team fix this issue, you can star this issue on the Chromium bug tracker.

In the next version due out in a few days, the problems of tabs sliding around for no good reason should be entirely or mostly fixed. 

In the current version they are only supposed to slide around to keep the tree in the same tab-order as the tab-bar. But the current version has some bugs that cause the tabs to slide around when they should not / when you did not ask them to. Those bugs should hopefully be all fixed in the next version.

In the next version due out in a few days, the problems of tabs sliding around for no good reason should be entirely or mostly fixed. 

In the current version they are only supposed to slide around to keep the tree in the same tab-order as the tab-bar. But the current version has some bugs that cause the tabs to slide around when they should not / when you did not ask them to.