Suggestion: allow users to move tabs to a window by right clicking and selecting a window name from a drop-down menu
Sidewise keeps crashing while using some websites. One of the culprits is:
Everytime I open any page on the MSDN website, Sidewise either crashes immediately, or shortly after. Hibernating the MSDN tab and then waking it crashes 100% of the time.
- Add the video-driver-causing-crash issue/solution to the upcoming FAQ
- Look for additional ways of reliably acquiring the correct favicon for sites like msdn.microsoft.com
I can find no way to get the window containing a tab to be raised (displayed, exposed, unminized) by sidewise, other then selecting the window row itself. I want to do it from the tab row because I often have many tabs in each window, and sometimes the window row is far away.
Can this extension be coded to work with out "reading every page that you visit"? - Medium alert Your data on all websites
Can the the extension work with out "reading every page that you visit"?
Your data on all websites
This item can read every page that you visit — your bank, your web email, your Facebook page, and so on. Often, this kind of item needs to see all pages so that it can perform a limited task such as looking for RSS feeds that you might want to subscribe to.
Caution: Besides seeing all your pages, this item could use your credentials (cookies) to request or modify your data from websites.
Essentially, Sidewise requires this level of access because it has to communicate with each individual tab/page for various pieces of information that are used to construct and display the tree's contents.
For example, Sidewise uses the referrer (opening page's url) of each page to help it uniquely identify which page goes with which row in the tree (e.g. during session restore). Currently, this information can only be obtained in Chrome by asking each page for it. Similarly, Sidewise needs to communicate with each page to ensure that we have the correct page titles and favicons at all times.
Other features such as the Youtube timer also rely on this kind of page communication. And future features, such as "search text on all pages" from the sidebar, will require this permission as well.
The real problem, from an extension developer's perspective, is a lack of fine-grained control over what an extension needs to see on a page. Currently, it's basically an all-or-nothing affair. If I need one bit of information from a page, I have to request permission to see the whole page.
I will give some thought as to whether page-access could be made into an optional permission. Having it disabled would definitely impact some pretty core aspects of how Sidewise works, and I'm not sure the penalties in tree functionality/accuracy would be worth it. I suspect users might find the limitations it introduces to be annoying or confusing.
I will be open sourcing the Sidewise codebase in the not too distant future, at which point other developers can independently verify that Sidewise does not do anything bad with its access to these permissions.
Until then, the best I can offer you is my personal promise that Sidewise does not, and never will read or collect any of your personal information without your explicit permission.
Just realised I can get a cleaner look by putting Chrome in full-screen mode - when on the right hand monitor, sidewise sits on the right-hand edge of the left monitor, and gives loads of browser space, plus easy access to tabs.
Now, if sidewise could replicate the bookmark and/or toolbar from Chrome, there'd be no need to have the chrome window at all!
Glad you have found a way that works well for you.
A bookmarks sidebar pane is definitely on the todo list, though replicating Chrome's own bookmark-bar probably won't happen.
Customer support service by UserEcho