@yngve said in Sadly, I will be leaving Vivaldi...BUT NOW I'm back after some fixes.:
@RasheedHolland said in Sadly, I will be leaving Vivaldi...BUT NOW I'm back after some fixes.:
should I simply respond to the emails that I received from the Vivaldi team?
Yes, you should.
As I said above, our testers may have missed a step (or configuration) that is so obvious to the reporter that they never thought to mention it in the report, or there is a misunderstanding, or the problem occurs on one platform, and not another. (And keep in mind that testers frequently use clean, default profiles when testing; no extensions, no changes to the settings, on their OS, which may be Mac, Linux, or Windows, so if any of those are needed: Tell us.)
BTW, @jane-n is one of the main Vivaldi moderators here in the forums, so yes, I know her.
OK cool. I think I responded to some of the emails, but I didn't get any reply. Also, I don't think that any of these bugs are caused by third party factors like extensions. It's just a matter of assigning some developer to fix these bugs. And yes, JaneN is very helpful, she always try to respond to questions on WSF, even if it's weeks later, I appreciate this.
@DoctorG said in Sadly, I will be leaving Vivaldi...BUT NOW I'm back after some fixes.:
@RasheedHolland said in Sadly, I will be leaving Vivaldi...BUT NOW I'm back after some fixes.:
VB-102809
Yes, bug still unfixed. I tested and updated bug tracker for latest internal 6.8 dev version.
Yes, I was afraid for this, thanks for updating the bugreport. 👍