@ratti How is a notification window that appears for 5 seconds or so annoying? You click the download link (choose the download location or always download it to the same place), then when it's finished, Vivaldi tells you. Then you can open the downloads folder if you wish or just let the notification disappear and get on with your work.
If you found a bug, please report the issue to the developers to fix it.
How to do a bugreport for Vivaldi
Report each bug seperately at https://vivaldi.com/bugreport/
Describe the issue as precise as you can.
Add some information about extensions you use.
Add information about the operating system and version you use.
If you have problems with video or audio give us information about your installed codecs and graphics card/GPU.
Add a exact link to the page where the issue comes up and can be tested.
After reporting the issue, you will receive a confirmation mail from the bugtracker.
In a reply to this mail you can add more information and files (like screenshots or testcases) as attachments and it will be added automatically to bug report.
If you have questions about the bug please ask in forum first and do not forget to post the VB-XXXXX bug number (you can find it in confirmation mail).
Thanks in advance for helping us to make Vivaldi better!
Feature Requests are wonderful - but I think Vivaldi needs to do a reality check and perhaps consider another approach going forward.
The reality is:
Vivaldi has a small development team that’s busy and at capacity.
There are major new features (Mail, Sync, Mobile?, and likely others) that are still in the works, at various degrees of completion, that need to be completed.
There is a huge list of bugs (even after triage) that still need to be fixed.
There's a practical limit to the number of new features that can make it into a snapshot cycle, and that's only if the next Chromium release doesn't cause major issues.
Vivaldi has probably received enough feature requests to keep them busy for YEARS. Some of those feature requests likely merit their own version number.
Chrome/Chromium 59 will get released next week and we still haven’t seen a Vivaldi 1.10 public snapshot build based on this code base.
Feature Requests serve to keep the Vivaldi community engaged and Vivaldi gets indirect feedback about product sentiment, but that’s about it. The threads get unwieldy and there's no feedback (in the reverse direction) as to what ideas are being considered in short-term or long-range product plans.
At this point, we’ll be better off if Vivaldi simply publishes a Roadmap (subject to change at any time) outlining what suggestions they plan to implement next. (They can still have "secret plans" that they withhold for competitive reasons.)
As Vivaldi progresses, people will still share their feedback (as they have done in the past) and Vivaldi's priorities, in turn, will evolve and change.
@x-15a2: Unfortunately, those links are all we have, because the community admins are the only ones at the moment who have the power to change email addresses. THEY ARE WORKING on changing that. Unfortunately the software is stubborn, and once signup email was set as your unique identifier, changing that standard is a little bit of a nightmare.
Please feel free to contact them again and urge them to handle your personal case. I know they want you to be satisfied.