Regress this, regress that
Every new beta version has at least 10 new regressions. At this rate when you release official v1.3 it will have more regressions than it had on the first day of releasing the browser 1-2 years ago. So far I didn't care much abot regressions but the last one is a killer (using the address bar as a search box is now dead) and I think I'll stay with 1.3.551.13 for the next 10 years until you stop making regressions. I've got the feeling you work exactly like Mozilla - doing whatever you want. But this isn't the way to make your browser popular.
The address bar search is working fine for me.
If you're not up to testing snapshots you should stick to using final builds, but don't bother reporting bugs at all because many bugs are fixed in each snapshot.
You don't even know how to report bugs. Ranting is useless. People need a recipe to reproduce any alleged bug before it can be fixed. If there were no bugs or regressions to report there would be no point in releasing snapshots. Hopefully, release candidates will be free from regressions.
I know how to provide bugs and whenever I'm sure of the steps to reproduce I include them in the report. But it seems pointless to report since someone said they had reported the disappearing close tab button a year ago and they fixed that only recently.
I am up to testing betas but not when the newer version has a number of features removed from the previous one.
Regression: the act of going back to a previous place or state.
Given that there are, literally, thousands of 'states' in a modern browser program, changing code in any one place has the potential for breaking code somewhere else or in some obscure operating mode - in some cases, resulting in a patch to an older problem to be itself broken or omitted and causing the older problem to reappear. That is a regression. Such things become more likely when two different developers are working or impacting the same code module for whatever reasons.
Regressions happen during software development, just as other kinds of bugs happen. Just because a regression appears in a change-log does not mean it just suddenly appeared in the prior version… it may have been around for multiple versions, but just finally was successfully fixed.
Moreover, just because something formerly working in your particular program installation may fail to work after an update does not necessarily mean the software contains a true 'regression'.
One of the most frequent causes of regressions in Vivaldi is the continual changes in the Chromium codebase, which is changed every few weeks without any regard whatever for how it impacts Vivaldi.
… but the last one is a killer (using the address bar as a search box is now dead) ...
After one of the last snapshot updates this happened to me too. The real problem was the removal of the default search engine. After choosing a new default search engine in Settings - Search the search box and address box were working again as expected.