Yes, though it makes the process take longer, because it runs a "verify all clean" pass at the end of the first cleanup pass, and if there is another tab with an offending favicon, it goes through the same process-of-elimination routine again to find it ... repeat until a "verify" pass finds no more problems.

It could be more efficient than this, but given the probably very rare triggering of this 'feature' vs. multiple offender tabs, I'm OK with it as described for now.

I will take a crack at it this release cycle and as long as the solution isn't too complicated I'll have it in the next release. I believe it should be pretty straightforward.

Good idea. I will put it on the todo list. 

I've made a change for the next release which will do at least part of what you ask for here when the sidebar is undocked and you have the "keep sidebar visible" option checked: when you click rows in the sidebar, Sidewise will refocus the sidebar after the focus-switch takes place.

However, the main problem with this solution is that the sidebar popup is not truly an "always on top" window. Chrome provides no mechanism currently for extensions to make a window always-on-top. 

Thus when clicking on rows in the sidebar, with this solution in place, the popup temporarily disappears (because the main Chrome tab is focused and brought to the top) and then reappears (as the solution's code refocuses the sidebar). Also, if you then click on the actual page, the popup again disappears (goes behind). Which then requires clicking the Sidewise button twice to (close, reopen) the popup.

I am marking this as FIXING while in consideration of possible additional solutions:

- (Windows only) Make the Sidewise Helper AHK script (currently in development) set the Sidewise window to be always-on-top while Chrome is focused; this would be the best-functioning fix but only works on Windows and requires running my extra helper program

- Solve the two-click problem to reshow a hidden undocked sidebar: one possibility is to compare the dimensions of the Chrome window(s) and the sidebar to deduce whether the sidebar is partly or completely hidden onscreen, and if it is hidden, then clicking the Sidewise button should just raise the sidebar instead of closing it.

My 'quick' solution described in my main reply also works with hover preview and scroll-to-switch, though as I mentioned, the (currently unavoidable) popup disappearing/reappearing effect is a bit unpleasant ;)

I've made a change for the next release which will do at least part of what you ask for here when the sidebar is undocked and you have the "keep sidebar visible" option checked: when you click rows in the sidebar, Sidewise will refocus the sidebar after the focus-switch takes place.

However, the main problem with this solution is that the sidebar popup is not truly an "always on top" window. Thus when clicking on rows in the sidebar, with this solution in place, the popup temporarily disappears (because the main Chrome tab is focused and brought to the top) and then reappears (as the solution's code refocuses the sidebar). Also, if you then click on the actual page, the popup again disappears (goes behind). Which then requires clicking the Sidewise button twice to (close, reopen) the popup.

I am marking this as FIXING while in consideration of possible additional solutions:

- (Windows only) Make the Sidewise Helper AHK script (currently in development) set the Sidewise window to be always-on-top while Chrome is focused; this would be the best-functioning fix but only works on Windows and requires running my extra helper program

- Solve the two-click problem to reshow a hidden undocked sidebar: one possibility is to compare the dimensions of the Chrome window(s) and the sidebar to deduce whether the sidebar is partly or completely hidden onscreen, and if it is hidden, then clicking the Sidewise button should just raise the sidebar instead of closing it.

I've made a change for the next release which will do at least part of what you ask for here when the sidebar is undocked and you have the "keep sidebar visible" option checked: when you click rows in the sidebar, Sidewise will refocus the sidebar after the focus-switch takes place.

However, the main problem with this solution is that the sidebar popup is not truly an "always on top" window. Thus when clicking on rows in the sidebar, with this solution in place, the popup temporarily disappears (because the main Chrome tab is focused and brought to the top) and then reappears (as the solution's code refocuses the sidebar). Also, if you then click on the actual page, the popup again disappears (goes behind). Which then requires clicking the Sidewise button twice to (close, reopen) the popup.

I am marking this as FIXING while in consideration of possible additional solutions:

- (Windows only) Make the Sidewise Helper AHK script (currently in development) set the Sidewise window to be always-on-top while Chrome is focused; this would be the best-functioning fix but only works on Windows and required running my extra helper program

- Solve the two-click problem to reshow a hidden undocked sidebar: one possibility is to compare the dimensions of the Chrome window(s) and the sidebar to deduce whether the sidebar is partly or completely hidden onscreen, and if it is hidden, then clicking the Sidewise button should just raise the sidebar instead of closing it.

Making Ctrl+(Shift+)Tab work as you describe when the sidebar has the focus is a great idea. Will add. 

Oh that's bad. Good find :D The cause turns out to be the favicons shown in the sidebar -- if one of them is from a "malware site", we get the malware warning page in the sidebar too.

I've created a kludgy-but-functional mechanism to detect and correct this problem and it should be in the next release. 

The solution isn't pretty but it works. Basically, when Sidewise notices that the malware page is showing in the sidebar, it will ask the user if they want to fix the problem.

Sidewise then loads all the tree's favicons into a new "testing" tab. If that tab comes up with the malware-page, then we know that one of those favicons is causing the problem. Now we split the list of favicons in half and test each half separately in the same way, to figure out which half contains the bad favicon. We continue this process by repeatedly subdividing the "contains the malware favicon" list in half, then again testing each half ... until through the process of elimination we narrow the list down to a single favicon that causes the malware warning.

At that point, we have identified the offending favicon, and replace it in the tree with the default Chrome favicon. Fixed!

Oh that's bad. Good find :D The cause turns out to be the favicons shown in the sidebar -- if one of them is from a "malware site", we get the malware warning page in the sdiebar.

I've created a kludgy-but-functional mechanism to detect and correct this problem and it should be in the next release. 

The solution isn't pretty but it works. Basically, when Sidewise notices that the malware page is showing in the sidebar, it will ask the user if they want to fix the problem.

Sidewise then loads all the tree's favicons into a new "testing" tab. If that tab comes up with the malware-page, then we know that one of those favicons is causing the problem. Now we split the list of favicons in half and test each half separately in the same way, to figure out which half contains the bad favicon. We continue this process by repeatedly subdividing the "contains the malware favicon" list in half, then again testing each half ... until through the process of elimination we narrow the list down to a single favicon that causes the malware warning.

At that point, we have identified the offending favicon, and replace it in the tree with the default Chrome favicon. Fixed!