BUG: When opening many tabs at once, the order of the tabs is not properly preserved...
When opening many tabs at once, the order of the tabs is not properly preserved. You can test this by setting new tabs to open to the right of the current tab, then use a custom hotkey like F6 for "clone tab" and press it rapidly to make many clones of a real webpage like YouTube. You will notice the position of the active tab doesn't stay at the far right end like it is supposed to, it gets sandwiched. Please fix.
[bug reported VB-56805]
@TsunamiZ Cannot reproduce.
What setting is enabled in Tabs, Cloned Tab Position: Next to Original Tab, or As Last tab?
cloned tab position = next to original tab
if you are testing this starting with one tab, and you rapidly clone it, the active tab should always remain as the far right end tab, which currently isn't happening consistently. instead, sometimes newly cloned tabs are getting placed to the right of the active tab, sandwiching it, which is an indicator that the order of the tabs is not being properly preserved.
remember, this happens when opening many tabs at once or rapidly. it is not a problem if they are opened slowly.
This problem is really messing up several of my workflows. I hope this bug is getting some attention.
I have this problem after last few updates, Arch Linux.
Cloned tab is opened as last tab, sometimes somewhere in the middle (not set this way in settings).
New tab (set in settings as last) is opened somewhere in the middle. Total chaos.
Disabled all extension and restarted Vivaldi, the same problem.
Is it possible it takes from the sync settings of another PC/Browser without showing it in the settings of the browser I experience problems with ?
Does it have something to do with this ?
It is not sync. My wife noticed the same problem and she is using only one Vivaldi instance, one PC.
Story goes like this (tested on one any specific tab only):
- Clone tab (wrong)
- Clone tab (right)
- New tab (wrong)
- New tab (right)
- Clone tab (wrong)
- New tab (wrong)
if you also experienced this bug, please upvote the first post to help get some attention on it.
@TsunamiZ Upvoting has no effect on "attention", it just means that you LIKE the post.
@Gwen-Dragon said in BUG: When opening many tabs at once, the order of the tabs is not properly preserved...:
Confirmed internally for 2.8 Daily.
What you should do is ask for an update on this bug status at
when you upvote a topic/post, you help get attention on it.
and no need to ask for an update on the bug status, because the bug is still not fixed.
Hi and no, you don´t get more attention for faster bug fixing.
2. The bug status can change at any time, most important are Closed, Verified, Assigned to a Developer, in Progress.
You post anything as bug anyway, feature requests, design requests and sometimes bugs.
Software development does not work like this, it more lead to get ignored from the developer.
i'm just saying that upvotes help get more attention on the issue in general.
Argue on some other topic, please. Or in Private Messages.
@TsunamiZ Upvoting has no effect on "attention" anywhere but in feature requests unless a user, for some reason (and I don't know anyone who does) displays their forum topics by upvotes. Rather, it only adds to the "reputation" of the user whose post is being upvoted, whereby soliciting votes on a topic is seen as bad form. When it comes to developers and staff, literally no one pays any attention to upvotes on topics outside of feature requests. No one.
the main use of any upvotes system is to help get attention to topics/posts--to help "add weight" to it. the user reputation score aspect is much less significant, especially since reputation score isn't displayed unless anyone actually bothers to view a user's profile. the reputation score is trivial in terms of practical functionality. but obviously, not everyone realizes this and their opinion may differ. in fact, it would be even better if there is no reputation score, so some users won't feel inclined to post certain things for the sake of inflating their own reputation score to feed their own pride, with the help of their forum friends.
@TsunamiZ I understand what upvotes are doing in your mind. I fear you do not understand what upvotes are (and are not) doing in the Vivaldi forum. You keep telling people to upvote things in order to accomplish something that upvotes do not accomplish here. Telling users that "upvotes help get more attention on the issue" is not a productive use of forum space. It's simply not true.
You may continue to do it of course, but in the real world more attention among Vivaldi developers and testers (who converse with the developers daily) is generated by multiple reports of an issue, even when these multiple reports occur in the same thread as others, than by upvotes. In fact, upvotes are pretty much entirely ignored backstage, as a measure of the importance or impact of an issue. In six years of daily interaction with Vivaldi devs concerning this or that issue, Votes have never been mentioned. Ever. What has been heavily taken into account is how many users have reported something, what platforms they have been on, and what kind of detail or replicability their reports have included - like, what exactly was this user doing, on what kind of platform when they encountered the issue. And what, if anything, worked to solve or work around that user for that issue? This creates a universe of data within which one might navigate toward a fix.
That said, you do whatever you prefer to do. But I don't recommend telling users to do something that will generate no progress toward a solution for them.
upvotes are just one of several ways for getting attention for an issue. i am quite aware that they are not the most important thing, but they still help to some degree. example, in the case of this bug report topic, anyone experiencing this issue should add to the tally of confirmed cases by leaving a reply and an upvote on the first post. if they feel too lazy to leave a reply, then they should upvote the first post, at least. not every reply is counted as a separate confirmed case, so that is why it is important to add an upvote to the first post to help give a quick overview of the number of confirmed cases in the topic. so my request to users of confirmed cases to add upvotes on the first post makes perfect sense.
not every reply is counted as a separate confirmed case,
Yes, it absolutely is. If a user relies "this is happening to me" and describes how that is true, it is, every time, a separate confirmed case.
It's votes that are not counted. And no, this is still a false statement: "upvotes are just one of several ways for getting attention for an issue. i am quite aware that they are not the most important thing, but they still help to some degree." Votes do not get attention to an issue. I'm sure you feel they do. They don't.
so far, this topic has 21 posts--but that doesn't equal the number of confirmed cases, which so far is 4 upvotes +1 by the first post. that is what i mean when i said "not every reply is counted as a separate confirmed case, so that is why it is important to add an upvote to the first post to help give a quick overview of the number of confirmed cases in the topic".
anyways, your opinion may differ. but i explained this well enough already, and it is all i have time for.