Sorry this happened to you. I'm still trying to figure out why this (rarely) happens, and have a couple solutions in the works which are likely to fix this (and improve performance besides). Thanks for the report; I'll update you when I have something more definitive.

What operating system are you using?

I'm in the process of making some changes to how Sidewise stores its data that has a high probability of alleviating this problem.

How annoying! :D

OK, I will try to implement it differently (click focuses and then sends the click through) in the near future.

I have just released an update that adds a "Focus sidebar on mouse hover" option. Hopefully this is the behavior you guys are looking for.

Based on reading through your descriptions of how OSX behaves, I decided not to make this option also unfocus the sidebar when the mouse pointer moves off it. Since you describe Chrome itself as behaving properly with respect to receiving clicks while unfocused in OSX, this will hopefully still work fine.

Please let me know whether this is working as desired now. This isn't exactly "focus sidebar on click and then also click the item" as requested, but in contrast to that solution, my current solution should enable visual row-hover effects and tooltips to work as expected in the sidebar.

Unfortunately, Chrome provides no way for extensions to hide Chrome's own tab bar.

I have been investigating ways to "hack around" this issue by e.g. using an external script to modify Chrome's window-contents, but so far I haven't found a solution that really works.

Unfortunately this pixelated-icon behavior seems to be a Chrome behavior that can't currently be changed.

Basically, whatever icon I give to Chrome as the "window's icon" gets resized to 16x16 by Chrome; and Chrome then uses that downsized version for the window's icon in the OS. So no matter what resolution icon I use, Chrome just downsizes it to 16x16 and we end up with a pixelated icon in the OS's taskbar.

Marking this as under review for later investigation, i.e. if/when Chrome changes this behavior.

Planning to rework this option a bit and/or turn it into more than one option to give finer grained control, e.g. different behaviors for when the bar is already visible versus when it isn't.

Definitely want to add this. I agree it would be very helpful to have this functionality, and also have it key-bound.