For some reason my tabs positions jump around while I'm using them in Chrome. I'd like to request they stay in the position they were opened or dragged to. Thanks!
With the latest release I have fixed the most common cause (that I am aware of) of unwanted tab reordering/jumping. I'm pretty sure there are still at least a couple other (rarer) causes of this, so I'm still looking for those, as well as formulating a plan for how to prevent this problem completely going forward. If my new plan works, then Sidewise should become immune to tab-jumping issues regardless of other bugs in Sidewise (or changes in Chrome) that can currently cause the problem. For example, one general issue is that if Sidewise somehow fails to add a newly created tab to the tree (e.g. Chrome doesn't notify us about it), that can currently induce tab-jumping problems because Sidewise's tab order is out of sync with Chrome's tab order. My plan will prevent circumstances like this (which are essentially unavoidable as Google evolves the Chrome Extension API) from leading to the tab-jumping behavior.---I really want to get this problem fixed but it is a difficult one to reproduce. So far I almost never see it occur here, and can't reproduce it reliably. I'm going to try some new methods of "forcibly" causing Sidewise to do this bad tab-jumping behavior this week to see if I can trace down the exact cause and/or appropriate solution.
Same on Mac
I believe what is happening is that if you rearrange tabs by dragging and dropping them normally (using Chrome itself instead of using the Sidewise sidebar), Sidewise moves them back to where they were, at some short (~5 second) interval.
This makes Sidewise unusable for me, so I would also like it to be fixed.
...Or if a new tab is opened via middle-clicking a link. Chrome and Sidewise fight on where the child tab will go??
I really want to get this problem fixed but it is a difficult one to reproduce. So far I almost never see it occur here, and can't reproduce it reliably. I'm going to try some new methods of "forcibly" causing Sidewise to do this bad tab-jumping behavior this week to see if I can trace down the exact cause and/or appropriate solution.
Yes, its happening after rearrange tabs by dragging and dropping them normally
Still jumping, and now not display tabs after jumping-tab. If move tab after not-visible-in-sidewise-tabs — tab jump back.
When move tab by dragging and dropping them normally to the End (make Tab last) — Sidewise not accept this. Maybe it's general problem?
Happen to me too. I believe the problem is that Sidewise puts these tabs that jump into something like a sub-directory path in Sidewise. This is what I noticed, so hope this provide some visible feedback to you for your investigation.
As of today (11/24/2015), my tabs are also still moving around on their own. Is it possible to just put in an option that prevents the app from changing the indexes on the tabs? I recognize the value in putting the tabs in the same order as they are in the hierarchy, especially when users like me have a zillion tabs open, but it can also be irritating when I'm trying to debug something, and the tabs keep changing order. Thanks!!!
still have this bug as well
I also still have this issue on Mac OS X El Capitan 10.11.3, with Chrome 49, and other OSes.
It's been happening for a while, and it seems to be related to a tab de-sync issue. This may be caused by Sidewise not staying up-to-date with Chrome, and the browser may have changed or add tab events that Sidewise does not handle.
A better culprit however, may be Chrome's Recovery or Restore feature, trying to re-open all tabs that may have been lost due to a previous crash. I'm not sure, but this may have been introduced at a certain point after Sidewise started development, and just wasn't accounted for? Just speculating...
I may have even noticed this on some other operating systems, and tried to prevent it from automatically re-opening these tabs. If I was successful in preventing that, I could see the old tabs in a hibernated window in Sidewise. This would be useful, and to keep Sidewise in sync with my browser, and to continue using the integration, I could simply wake the window and use my old session from there.
I have also found a way to restore single pages at a time, but it is a bit time-consuming, and not effective enough for dealing with many pages at once.To do this, I simply open a new window, drag the target tab to there, close the tab, and the reopen it to have it appear in Sidewise. Then I can move it back to the original window I was working with to some varied success.
I would rather like to see this issue fixed, but I see development has stalled somewhat, and we may just have to either fix it ourselves, or use an alternative such as Tabs Outliner.
My tabs are jumping practically every time I open a link, and by disabling extensions and re-enabling one by one, I have confirmed that the culprit is Sidewise.
This is quite the deal breaker. :-(
I really want to get this problem fixed but it is a difficult one to reproduce. So far I almost never see it occur here, and can't reproduce it reliably.
First, thanks for your work and effort on creating and maintaining this plugin. I enjoy being able to open sets of tabs that are all related (like all my monthly billpay/finance, pay my bills, close them all).
I'm experiencing this tab jump, but not while I'm using chrome. It only happens when I completely close chrome and restart it. Suddenly there are a lot of "dead" tabs introduced in sidewise that don't appear in the actual tabs, and the order of everything is mixed up.
It's nice that I can use sidewise to click the X on the dead tabs and drag my tabs back around to the order I want, but it would be better if this weren't happening.
I'm open to you giving me a debug version of the plugin and sending you back the debug log if this will help you figure out the issue.
It happens every time I've used chrome for a little while (visiting sites, closing tabs, etc) and then restart it, so I'm sure you'd enjoy a no-false-positives log file.
One thing I haven't done is purposely observed sidewise before I shutdown chrome to see if the dead tabs are there before close, but I can say I never noticed these dead tabs before shutdown. I'll pay more attention to this detail the next couple times I restart chrome.
Customer support service by UserEcho