We will be doing maintenance work on Vivaldi Translate on the 11th of May starting at 03:00 (UTC) (see the time in your time zone).
Some downtime and service disruptions may be experienced.
Thanks in advance for your patience.
Happy holidays: Vivaldi browser Beta 2 is here in time for holidays
-
Hurray! Well done and happy Christmas to all!
-
Hurray!! Merry Xmas to all at Vivaldi! Thank you very much!
Will installing the Beta2 stop updates to the next snaphots? -
zero reasons? That is not much.
My reason why viv already is my first browser, is to test it under everyday conditions, maybe find some bugs and help making it better.
It isn't perfect but for the parts where I think that viv doesn't have the ability to give me the web experience that I want I have a second browser.And speaking for myself I am already annoyed by other browsers when I surf the web, because I use tons of shortcuts and most of them support only little useage of shortcuts- even less have the options to fully customise them.
-
Confirmed as well, can't update from 1.0.303.52 (Beta) (32-Bit) to this one on Win 8 x64.
-
Yes, it says that for me too, but the numbering is STILL 1.0. Is this really the Beta for Vivaldi 2.0 or is it still for 1.0?
And why have a Beta 2 for Vivaldi 1.0? What does that mean? I thought they were gonna go straight to final.
-
thnx:)
-
With this build, i get slow tabs opening, you can see how clicking on tab draws window slowly. We had this behavior before, i guess its back now.
Still no mid click for new tab.
Still web panel has padding before right clicking icon.
Basically, i am back to first beta, sadly.
edit: and since there is no link for first beta i am stuck with this version…
-
And why have a Beta 2 for Vivaldi 1.0?
That's normal, more betas are likely on the way, since users expect Vivaldi 1.0 to be still limited in features, but stick to its dev road map and be relatively clean of reported bugs, and it takes time to do. Thanks Vivaldi team for the update!
-
Update: Nvm, working now:)
-
What is the release version for Beta 2? If we're on snapshot (currently 1.0.344.34), is that ALSO Beta 2? In my about window, I have:
Vivaldi 1.0.344.34 (Beta 2) dev (64-bit)
Revision 9ae925ff17ca36e328d999851001d0b9dae32e33 -
Thanks Jon, Happy Christmas all!
-
I have
Vivaldi 1.0.344.37 (Beta 2) (32-bit)
Revision 9ae925ff17ca36e328d999851001d0b9dae32e33 -
hello Jon von Tetzchner and team Vivaldi
Thanks. -
Hmmmm.
Vivaldi 1.0.344.34 (Beta 2) (32-bit)
Revision 9ae925ff17ca36e328d999851001d0b9dae32e33 -
I still remember hearing about Vivaldi back when it was just a feature-barren technical preview. Even then, I felt that great things will come out of it.
Keep up the good work, Vivaldi team. You've progressed so much in this year alone.
-
Thank you Jon and the team! Happy Holidays
-
Got it from here:
https://vivaldi.com/download -
Wait, so let me get this straight . . .
This is Beta 2 for Vivaldi 1.0, because the numbering says 1.0.344.37.
Does this mean that Beta 1 will become the final and Beta 2 will become the next 2.0? Or will this be final 1.0 and they will have the next Beta after that be for 2.0?
Why have more than one Beta before a final for that version? Why not just keep developing until you have the final?
-
Thank you Jon and Vivaldi team for this Beta. You surely have made my computing life better this year and I am grateful. From Canada, Merry Christmas to all here and a Happy New Year.
-
Because each Beta is a "pause point" where the unfinished product is considered relatively "safe" for public use. People who downloaded the first Beta and never updated after that are now getting notice of THIS update and will, in one jump, get all the progress since 1.0.303, right up to 1.0.344, without having experienced the various headaches and glitches we addicts saw, with all the snapshots in between. So far, Vivaldi is pursuing a linear development pattern, and it won't make sense for them to pursue multiple streams (if they ever do so) prior to the release of at least the first stable version. Don't be shocked if we see even a Beta 3 before the first stable arrives. "Stable" is kind of an important landmark. The product has to be really, really, really solid and trouble-free before final release to the general public.
