Open new tab next to active

What would it take for the usability-design team to understand that the intuitive behavior for Open a New Tab Next to Active is to open the new tab next to active and not x tabs away from the originating tab, outside the Tab Groups?

For example if I have a "News" tab group with Forbes, Vancouver Sun and some other news sites and try to open an article next to the corresponding magazine I would have to look for it outside the News Group, a complete feature-bug.

I included a poll to see what the rest of the user community thinks about this new feature/bug.

Moderator edit: moved from Opera for Windows/Mac/Linux » Opera browser

I vote for "in the same group". It's weird behavior when new tab is opened from a link in a page (when page is inside group) you are browsing and is placed outside of the group. I can agree of a new tab placement outside of a stack only when its new blank tab, but I should be able to change that in the Opera options.

It has been already requested here on the forums.
I hope they implement a new option specifically for this (instead of putting it as an "Open new tab next to active" effect).

I know this issue has been posted on at length ever since the feature of "auto" tab stacking was labelled as a "bug" by the Opera developer team and removed from whichever build it was in.

But the continuous pleas of Opera users to bring it back as an option (as well as having a user option to disable tab stacking altogether) have been totally ignored. In fact, a work-around that survived was also removed once it was discovered.

I hope I'm not breaching etiquette by restating some of what I've read in so many of the threads on this issue.

Was this "bug" affecting something else so critically that it had to be "fixed?" If not, why not just leave it alone? Even though it was considered to be a bug by the development team obviously many many users found it to be an incredible useful and well as logical feature.

This option obviously somehow made its way into a build: would it truly be that difficult and complex to put it back in? I'm not trying to be sarcastic here, I honestly would like to know. Because if it IS difficult and complex then that would explain why things haven't been changed back even after 10 months. And people would then understand why it hasn't been added back in.

I'm not familiar with extensions except as someone who uses many in Firefox, have no idea how to create one, but somebody who does have the expertise, could this feature be added via an extension? One of the Opera extensions that I absolutely love is "new tab on long press." To my technically-challenged mind, if tabs can be created via various methods (+ button, ctrl+T, right-clicking, and, via extension, by long-press) does that mean that manipulating the creation of a tab inside of a tab stack is also possible? Honestly, we have tab options right now. Does configuring the behavior when a tab is closed (focus to tab to the left of closed tab, focus to most recently viewed tab) mean that it should be easy to configure an auto tab stack/new tab opens within the stack option?

Next to my last point, I really want to be able to use this "bug" due to issues of productivity and convenience to the point that I'm willing to "downgrade" to the Opera build that contained it. Can someone point me to that build? Are there issues of security in using it? Is there a list of the "issues" that it had so I can determine of it's safe to use?

Finally, I know that Opera is a much smaller enterprise with a much smaller market share than Firefox. But even with Camino (a web browser I love that will probably be going away soon) which is probably even smaller, there is interaction between the developers and the community of users. The developers are part of the community of users. That has to be the case here as well. Does the Opera team not have people who feel the same way about the convenience and utility of that former "bug"? I guess I'm surprised by the complete silence regarding this. I'm brand-new to the Opera user community and maybe I'm completely out of line here but I get the feeling of indifference of the team to the users. I don't expect a personal hand-written letter from them in response but some acknowledgement would make me feel less like as Opera users we're supposed to sit quietly and accept whatever they decide to dole out to us.

As you can tell I tend to go on when I get started talking. To everybody who's made it to the end of this post, especially any member of the development team, my sincere thanks for reading.

Originally posted by anotherchris:

But the continuous pleas of Opera users to bring it back as an option (as well as having a user option to disable tab stacking altogether) have been totally ignored.

No, we can't be sure whether it's being ignored or was already added internally and just haven't been published on the public branch yet or if they're planning to do it.

Originally posted by anotherchris:

The developers are part of the community of users. That has to be the case here as well. Does the Opera team not have people who feel the same way about the convenience and utility of that former "bug"? I guess I'm surprised by the complete silence regarding this.

You have a valid point here!

Sure, that is one thing that should be added (replaced).

Another release, same problem.

It seems that I would have no choice but to drop this little browser after all.

There was a time when it was the most innovative/usable browser out there but now there's just too much "features for the sake of new features".

Originally posted by Meridivs:

Another release, same problem.

11.52 is only a small security release!

Opera 12 is here...

Same idiotic Open in New Tab "feature". Somehow we thought they would listen to their users by now.

Being the first tabbed browser doesn't mean it should be the last one standing.

As of now there are better browsing experiences out there with less site-compatibility problems and good usability teams that know how to listen. Too bad Opera couldn't keep up the pace with it's users.

P.S. This Reply was posted from Google Chrome, for some reasons the new Opera 12 couldn't handle it's own Community Forum?!

Originally posted by anotherchris:

I really want to be able to use this "bug" due to issues of productivity and convenience to the point that I'm willing to "downgrade" to the Opera build that contained it. Can someone point me to that build?

Don't know if you really want to downgrade that much: 11.01 was the last "good" version where a new tab would open in the tab group, not next to the tab group. This was changed in 11.10 - no mention in the changelog. There must have been a compelling reason to drop this feature since the devs seemed to have been proud of it and advertised it in the help file.

I have nothing against this feature request, but its easy enough just to drag a link from the current page and drop it after the current tab on the tab bar, thus keeping it within the group.

I have found Opera extension called AutoStack which is a workaround for our problem. It moves new tab opened inside stack next to active.

Thank you Yanek! I'll give it a try ASAP.

Meantime the new Opera 12 keeps hanging on my system (a Toshiba A300 with Core 2 Duo and 4 GB of RAM). I guess there are a few site-scripts that are simply not compatible with this version of Opera (I'm browsing with all Flash/Shockwave Plug-Ins disabled).

I guess that if they don't solve this in the next patch we would have to donwgrade to a more stable version - this never happened in previous versions of Opera.

+1 to:
open new tabs in the same tab group.

that's what groups ar for...

Solved the problem with AutoStack, great Add-On!

Unfortunately Opera 12 is too buggy to use as a regular browser - it keeps crashing (same windows as previous versions) and cannot display more than 50 products on an eBay page without screwing it up or... you're right, crashing again!

Maybe I'll open a new thread for this or just quit doing someone else's test work and chose another decent browser.