A bug’s life at Vivaldi
-
Well... the first thing to do would be not using 3rd party Cookies in here i guess... since i guess many peeps have those disabled.
And just a very small thing that you could do; enable back/forward function in speed dial folders, it's annoying that when you enter a folder, the mouse "back" doesn't work. -
@cail Actually, Vivaldi doesn't "use 3rd party cookies." They use a single login protocol to sign you in to two different domains at once - vivaldi.net, and vivaldi.com. It doesn't matter which side you sign in from, setting a "signed in" cookie on the other side will make that a 3rd party cookie. Half of the community content is in one domain, and half in the other. To "not use 3rd party cookies" they would have to either make you sign in to each domain separately, (which might create a problem using the same profile ID and password for two domains), or cram everything from both sides into a single domain. For my part, I'm not bothered by the current setup.
-
I've also filed bugs for UI changes/improvements in the past and inquired about their status only to learn they had been closed as Invalid/won't fix. However, I don't think that these were being ignored but rather taken into consideration for future improvements.
(Edit: I'm not talking about UI bugs that I've filed for things that broke unintentionally. Those usually do get fixed very quickly.)
To add to @Aronand 's followup, just because a bug gets closed in the bug tracker doesn't necessarily mean that it's dead. Bug reports, combined with feedback received from forum discussions and feature requests, do get incorporated into future releases.
So, filing bugs and discussing them here in the Forums really does work... even though it might sometimes take a while for our suggestions and feedback to become reality.
-
@cqoicebordel said:
Finally, Vivaldi believes that a "good bug" is a bug that'll be filed again. Even if the first one is closed (by mistake or not), if it impact multiple persons, if it's important enough, somebody else will file it, and thus, there is another chance of fixing it.
I'd replace the "that" with "if" - i.e. (...) if it is a "good" bug it will be filed again (...)
One of the problems of fixing bugs is that the developers need to be able to reproduce it so that they can see what is broken - which can be really difficult sometimes. There were some bugs that were in since years and got tons of bugreports, but it was still impossible to fix them, no matter how detailed the description of the reporter was and which additional data they sent - because nobody was able to reproduce them until someone finally stumbled upon the real trigger by accident (I think especially about one of those "sometimes" bugs)
-
@quhno said in A bug’s life at Vivaldi:
One of the problems of fixing bugs is that the developers need to be able to reproduce it so that they can see what is broken
I have seen a lot of bug reports (for other products) closed because the developers could not reproduce them. Often, this was because my report was too brief, or was misunderstood in some way. However, because I received a report that the bug had been closed, I was able to follow up immediately and convince them that there was indeed a bug.
There's a good chance that the same bug reported six months or a year later by someone else will just get closed again.
-
- Enter chrome://settings/content/cookies in the address bar
- allow:
[*.]vivaldi.net [*.]vivaldi.com
After that you can use the central login even with 3rd party cookies disabled.
-
@pesala said in A bug’s life at Vivaldi:
There's a good chance that the same bug reported six months or a year later by someone else will just get closed again.
As we usually don't close duplicate bug reports but set them as duplicate (provided the reporter has chosen a sensitive title and steps so that we can find the duplicate) we see if there are more reports about something - which definitely raises the awareness that there might indeed be something that causes it.
-
@hekel: Hey, all the feedback in this thread is very useful for us, we are listening
-
We have in house test automation system similar to RobotJS and AutoPy. It relies on visual pattern search, color search, image comparison and controls mouse, keyboard and touchscreen.
System is mostly written in JavaScript and uses Node.js, but a few platform specific and/or performance critical parts are written in a number of different languages form C to AppleScript.
It's mostly used by QA for automating interactive tests. We have over 22000 tests that catch over half of regressions. The rest is catched by QA, developers, Sopranos and users.
We run tests continuously on x64 machines running Windows, Linux and Mac and ARM development boards running Linux.
Besides that developers write Unit tests in Jasmine testing framework and those tests also help to catch regressions.
-
@gwen-dragon said:
@derday said in A bug’s life at Vivaldi:
VB-34514
I voted in bugtracker for this.
Hi, can you give me news on VB-32651?
Thank you.
-
@ayespy: from a purely selfish point of view, I would much rather they put everything in vivaldi.com since my corporate firewall blocks vivaldi.net (and hence sync)...
-
@gwen-dragon said in A bug’s life at Vivaldi:
@folgore101 said in A bug’s life at Vivaldi:
VB-32651
Is related to bug VB-24319 "[Windows] Can not stream Videos From amazon prime"
Work in progress to fix it.Thank you.
-
@olgaa I sincerely hope so, since I enjoy Vivaldi and I want it to become more reliable as it's the only browser I use outside of testing/debugging code. In the past I've watched release candidates introduce regressions and seen "stable" releases get pushed less than a day later... before any real testing could even occur. It's a wonderful browser with a great vision, but the bug handling/testing process is Vivaldi's biggest flaw IMHO.
-
@hekel The calendar is forced by Chromium intakes. Vivaldi is not at liberty to set their own release schedule entirely.
-
@giorgi: Thanks for the info!
-
@christoph142 said in A bug’s life at Vivaldi:
sending status updates to the reporter's mail address is very much possible. We have been discussing this internally a few times already and I'm going to continue being an advocate for this.
This is something that I have been wondering about for quite some time now. If a user reports a bug or thinks they have found a bug it makes perfect sense to keep the bug reporter in the loop. Simply assign the users email to the VB number and voila the reporter is instantly kept up to date. And, please keep advocating for this to happen.
Now I reported VB-35804 Sadly sometimes no news is not good news.
-
@para-noid I also agree that it would be great for users to get an update on their bug's status, even if it's just to notify you that the bug has been confirmed, and especially important (for everyone concerned) if you file a bug for a serious issue and it gets closed with a status of "cannot reproduce".
Also, if you file a bug and would like to provide some additional information to the developers, you can always reply to your bug confirmation email and include those details.
That said, the bug tracker is not used for discussion so you really, truly are not missing out on anything exciting between submitting a bug and seeing the fix appear in a Snapshot. You may also find this surprising but most of the interesting discussions about issues concerning Vivaldi actually goes on in these forums. It's the nucleus and nexus for the entire Vivaldi community and a critical resource for everyone. If you're running into an issue, it important to discuss it here, and to confirm issues that other users report as well.
-
One more argument, why clients like to know about the state of "their" bugs:
I am interested in these states:- Not reproducible
It may indicate that the problem is either with my machine or I should work on my way to explain problems - Duplicate
I can forget about this, somebody (probably) looks out for it - By design
ok, not a bug
- Not reproducible
-
@para-noid: Your issue got closed as "Cannot reproduce". But honestly, it's more of an "Invalid". If you experience an issue, please ALWAYS test without any extension and only submit a report if it still happens. (This coming from an extension developer!)
-
@christoph142 said in A bug’s life at Vivaldi:
@para-noid: Your issue got closed as "Cannot reproduce". But honestly, it's more of an "Invalid". If you experience an issue, please ALWAYS test without any extension and only submit a report if it still happens. (This coming from an extension developer!)
Thanks. Will do.