0

Discarded Tabs

Zach Hunter 4 years ago updated by Christopher Bauerschmidt II 4 years ago 1

Chrome added tab discarding last year. This is great for memory, but maybe not so great for sidewise. When Chrome discards a tab as described here: https://developers.google.com/web/updates/2015/09/tab-discarding?hl=en it loses it's connection to Sidewise. If the sidewise tab is hibernated and brought back, it actually opens a duplicate tab, leaving tabs open in Chrome that Sidewise cannot control.

I can verify from my machine that disabling tab discarding fixed this issue with me. It seemed that once a tab was discarded (which actually happens when you open a few tabs and don't immediately click on them but wait a few seconds or interact with an already open tab) it lost all connection to Sidewise and any future tab opened from that one was never seen by Sidewise. Compounding this is the fact that Chrome considers Sidewise to be a tab itself meaning Chrome was discarding Sidewise.


  • [App] Sidewise Discard (4 discards this session)

Also, disabling this seemed to fix the issue of Sidewise not docking to Chrome.


Disable by going to chrome://flags search for discard and select Disable.