Bugs in most recent versions of WebStorm?

[jrista]

I am a real fan of this plugin. I've been using it for a while now, and it is definitely a time and tab saver.

That said, in the most recent versions of WebStorm...those released say starting about the middle of this year, maybe late spring, it seems this plugin has broken. When switching files with ALT+S, it no longer switches properly.

For one, the position of the tab will shift now. So if you are in the first tab in your list of tabs, and hit ALT+S, it will often switch to the second tab. I think generally speaking, it shifts to the right of the tab you started on.

Worse, though, it seems to get confused about exactly what set of files you were cycling through. So it will shift the tab, but sometimes it will also switch to cycling through an entirely different component. So this can lead to some confusing behavior, especially if you've been working on multiple components.

When you have only one tab open for a component, and use ALT+S to cycle through them, you can see the point where it decides to shift to another tab. It seems to always occur after cycling to the html. Interestingly, though, it seems to go from html, to the component class code...where the code opens in another tab, then as you continue to cycle it goes back to the html, then to the styles, then to the component code again...but here it remains in the same tab...then back to the html, after which the component code pops out into another new tab, then it goes back to the html.

So it seems there is some kind of broken cycle here, between the component code and the html. When this. cycle interferes with other components, it can get very confusing, and you can potentially end up in a situation where you effectively "walk the tab bar" from left to right if you somehow get stuck in a cycle of shifting from html to code, but the code might end up being for a different component, then cycle through again, end up in the next tab over for another different component, etc. etc.

[jrista]

Here is a GIF sample (Sorry for it being so small, mostly, watch the tabs) that demonstrates the problem. This problem did not seem to occur before...I think I started using this plugin either the beginning of this year, or later last year (maybe this time last year). It used to work great.