When I open Chrome, Sidewise opens automatically, but it now brings up lots of previously closed tabs ( the closed tabs now shown in Hibernated mode).
This didn't use to happen - seemed to start in the past few days.
How can I stop this behaviour?
Have exported to a file but do not export to the interent
to synchronize tabs multiple browsers on different computers.
I for myself have finalized and implemented an extension function to export all settings and tabs in https://docs.google.com/spreadsheet, and import them back into the expansion of https://docs.google.com/spreadsheet
If anyone is interested please contact us by e-mail: email@example.com or share examples show modifying extension will be glad to cooperate with the developer
It may even allow for faster and vaster feature testing!
In my opinion, you're making the best tab manager out there, mainly because of the problems you're focusing on.
I frequenty click the close/hibernate icons accidentally when in fact, I only intend to select the tab.
This happens mainly because of the small width of my sidewise tree bar. I prefer this so as to reduce screen real estate.
It's nice if the hovering icons be made optional. Really useful also if you're already using shortcuts like "middle-click" to close tab.
I've been using Sidewise for about 2 months and have accumulated more than a thousand hibernated tabs. Before this problem of Sidewise not launching occurred I'd noticed that some of tabs I opened were not appearing in Sidewise. But, when I restarted Chrome and reloaded the last session tabs, the tabs previously not appearing could now be seen in Sidewise.
But now when I click Sidewise icon nothing happens. I tried restarting Chrome and also restarting computer but it still won't work. I'd like to try reinstalling Sidewise but I'm afraid that I might lose my hibernated tabs.
Please advise on how can I make Sidewise work again or how to recover my hibernated tabs. Thanks in advance.
As the title says, it might be better to use chrome.storage.local rather than localStorage. There's two reasons for this: chrome.storage is asynchronous, which supposedly makes it faster. But more importantly, localStorage is limited to either 2.5MB or 5MB of data. But if you use chrome.storage, you can use the "unlimitedStorage" permission.
Speaking from experience writing Chrome Extensions, chrome.storage.local is the best way I've found to persistently store user data. And if you're worried about it being async, it's easy to write a buffer so that the API remains synchronous, but behind the scenes it's still async. I can give more details if you like, including working code.
The idea is to make it easier to see...
Currently, when you have a lot of tabs, you have to frequently glance down!
This is inconvenient because we are usually focussed in the top left of the screen. (where the text starts on the page view).
As such, the best place to put the tabs we're currently working on will be near the top.
The older tabs should be at the bottom.
(The concept is similar to webpage design. The prime view estate is the top part. The bottom parts is not where the eye lands first.)
I don't have a date for this, but consider it on the priority todo list.
What I would really like to do is just rethink how the tab-ordering/nesting logic works overall, and create options for each specific case, e.g. "where to place new tabs opened via address bar", et al.
Customer support service by UserEcho