Bug: New Tab Position Broken v3.5.2088.7
-
@Gwen-Dragon
A fix is ready for a next 3.5 version.
Looks like this is still a unresolved issue, even with two new snapshot releases since that statement. Current build is
3.5.2115.4
and it appears to be still broken, at least for me.Is there any ETA or news about a fix, like did you guys rolled out a fix but it just didn't worked? Because the changelog doesn't say anything regarding a new tab position issues/regression.
-
@Gwen-Dragon Thank you, guess I gonna switch back to stable for the time being, as this issues messes to much with my workflow.
-
@Gwen-Dragon Wait, why do you link me the "How to report a bug"-template? It's a known bug confirmed multiple times by yourself, with the tracking number VB-73739
I mean I can keep on spamming the reports, but it will not help you in any way. Or am I'm missing something here?
-
@Gwen-Dragon .....
Okay, I re-reported it. New tracking number should be VB-74542 and this time I even linked some GIF's. I hope this ticket gets only closed when the workflow shown in the GIF's is not broken anymore.
-
Subscribed to this thread.
I'm also experiencing this issue. But it is more severe than just [As Last Tab].
In certain conditions it just stops showing the new tab at all.
And tabs can't be dragged in the Window panel.
And tabs can jump to the beginning of the list after restart.Which means something absolutely seriously broken.
It makes me wonder what was "Fixed" in VB-73739 and why the issue persists for almost a month already without much attention. -
They took a shot at fixing this in Thursday's build, but I think it's a partial fix at best. Fortunately, there's still a good ways to go yet before release, so I expect that they'll be able to finish the fix.
-
@rseiler said in Bug: New Tab Position Broken v3.5.2088.7:
They took a shot at fixing this in Thursday's build, but I think it's a partial fix at best. Fortunately, there's still a good ways to go yet before release, so I expect that they'll be able to finish the fix.
Reported by someone as VB-74396, incidentally.
Still no confirmation if Vivaldi really considers it fixed and the bug closed....
-
@Gwen-Dragon That's a problem then, since multiple people said otherwise in the same thread where it was announced fixed, and it's easy to demonstrate that it doesn't work.
"Opening new tab next to active tab in foreground" broke in an earlier build but still is. I guess it's under some other number now, but it would be more efficient to run this under one number. And who knows, the other one, even though it would have the same problem, may not even have been noted yet.
-
@Gwen-Dragon I'm sure it's already been done, including VB-74396.
Vivaldi needs to recognize when something they say is fixed isn't. Unfortunately, they haven't said a word that I've seen, but dozens of messages on mail....
-
If everything worked then the ticket VB-74542 should have updated information regarding foreground tabs that wont open next to the active tab.
Reproduceable via Crtl+T (New empty foreground tab)
or opening Bookmark via context menu in a new tabI added those information's via an email update to VB-74542. Hope Gwen does not chime in here and tells us that VB-74542 got closed as well (unless it was already a duplicate).
-
@Gwen-Dragon Does that make sense to you? One not a bug, one a bug? They either both have to be or not to be.
-