1.14.1077.45 was rushed out without fixing the bugs
-
Giving the benefit of the doubt regarding how critical it may have been to update Chromium and accepting that many new issues are likely related to Chromium64, I'd expect to see a huge focus on fixing regressions in Vivaldi's own code since 1.13 before a final 1.15 release then (regardless of chromium version). If it doesn't happen, then the core of the argument in this thread will still stand.
-
Just find it a bit weird that a crucial error like autocomplete URLs / search terms wasn't caught in cursory testing. Or is that just me?
-
@tjukken I'm an internal tester, and that bug never bit me. It never occurs in my setup. So, for my part at least, not all that surprising.
-
@purgatori said in 1.14 was rushed out without fixing the bugs:
I find it hard to believe that you wouldn't "give a damn" if an attacker/exploit was able to gain access to your machine or sensitive information because of an un-patched security hole.
I don't, because I am not paranoid about it, I never was infected since 1992, my PCs are not interesting targets for anyone, I have no secrets to hide on my PCs: I am not that stupid to place my bank account numbers and such important things on my HD . You can try hack me anytime, feel free to find all my mp3, jpgs, Commodore 64 scene warez and Vocaloid music videos you can leech from my pc anytime, if you can.
I am for sure more happy of current Snapshot 1.15 than the stable 1.14 because the annoyances in everyday usage were worst than having those patches stitched around a barely usable browser, because missing the features one uses everyday IS a dealbreaker.
15 days of delay won't have damaged anyone and this 1.15 SS released as stable would have provided a better experience and better user satisfaction than the actual 1.14.
-
@ayespy Ah, OK. Perhaps a reinstall is in order.
-
@ian-coog said in 1.14 was rushed out without fixing the bugs:
@purgatori said in 1.14 was rushed out without fixing the bugs:
I find it hard to believe that you wouldn't "give a damn" if an attacker/exploit was able to gain access to your machine or sensitive information because of an un-patched security hole.
I don't, because I am not paranoid about it, I never was infected since 1992, my PCs are not interesting targets for anyone, I have no secrets to hide on my PCs: I am not that stupid to place my bank account numbers and such important things on my HD . You can try hack me anytime, feel free to find all my mp3, jpgs, Commodore 64 scene warez and Vocaloid music videos you can leech from my pc anytime, if you can.
I am for sure more happy of current Snapshot 1.15 than the stable 1.14 because the annoyances in everyday usage were worst than having those patches stitched around a barely usable browser, because missing the features one uses everyday IS a dealbreaker.
15 days of delay won't have damaged anyone and this 1.15 SS released as stable would have provided a better experience and better user satisfaction than the actual 1.14.
So where DO you keep your important things?
-
@tjukken Probably not a reinstall (as that action has approximately a 100% rate of changing nothing), but more like a profile refresh or that sort of thing. With a recent update, it seems the default setting of "show drop down when typing" was turned off for some people as well.
-
@xyzzy said in 1.14 was rushed out without fixing the bugs:
Vivaldi makes every effort to fix critical bugs during the Snapshot stage. It's really easy to criticize Vivaldi but remember that once Chrome gets released, the next major Chrome release will be out (ready or not) in another six weeks. During that time, Vivaldi has to get their Stable release out, integrate (still buggy) Chromium beta code into a Snapshot, release follow-up Stable releases containing the latest Chromium fixes and their own fixes, and get the next Vivaldi snapshot (containing new features, enhancements and additional bug fixes) ready enough to test, and have a release candidate ready before the madness starts all over again.
Yeah but you're just telling us about what job Vivaldi as a company decided and agreed to do. They decided to compete with other major browsers, to use Chromium latest releases, etc. Vivaldi has to follow the trail of Chromium releases? Well, yeah just as any other browser vendor has to follow the trail of their own engines (including other browsers that use Chromium, like Opera), that doesn't mean you have a pass to throw a lot of regressions in a stable release all your users will have to deal with.
This will drive people away, because when something breaks in Vivaldi and works fine in another browser people will jump to that other browser not fiddle with forums and with trying to find a solution (mostly inexistent) or wait half a month for a fix to be released (still unreleased).
-
@rluik said in 1.14 was rushed out without fixing the bugs:
This will drive people away, because when something breaks in Vivaldi and works fine in another browser people will jump to that other browser
Not this little purple duck. I'm here for the long haul. In between V & anything else, there's just daylight & dust.
-
@steffie we don't count, we're hardcore V aficionados who like to test every V release, most people don't care what they use, they just care using something that works. You have to admit that 1.14 didn't bring lots of positive points in the eye of average joes&janes.
-
@ian-coog Yeah sure, i get it, but [to say something both cynical & serious simultaneously] V is a browser for "our friends", & real friends know what's really important, & are prepared to endure the lower as well as higher points along the journey. Ipso facto, those who are prepared to
jump to that other browser
were probably not really friends to begin with. After knowing, using & benefiting from the powerful capabilities of V, the thought of voluntarily giving it up & going back down the hill [waaaaaaaaaaay back down] to banal bland bleh browsers is anathema to me... & i believe to the majority of us "here".
-
@rluik said in 1.14 was rushed out without fixing the bugs:
... Vivaldi has to follow the trail of Chromium releases? Well, yeah just as any other browser vendor has to follow the trail of their own engines (including other browsers that use Chromium, like Opera), that doesn't mean you have a pass to throw a lot of regressions in a stable release all your users will have to deal with.
...In this case, it was a judgement call: quickly release a Vivaldi version into the 'stable' channel that incorporated the chromium 64 engine release providing a browser 'fix' for Spectre/Meltdown issues (and risk the major bugs inherent in that chromium version) or delay the Vivaldi stable release until all the chromium bugs were resolved or tweaks around them could be made. With nearly 140 Spectre exploits already uncovered as of 1 February 2018 (http://searchsecurity.techtarget.com/news/252434342/Meltdown-and-Spectre-malware-discovered-in-the-wild), and with that number certain to grow very rapidly in coming days, a strong argument could be made that issuing a secure 'stable-channel' version containing some bugs trumped keeping a major vulnerability window wide open for days or weeks until the bugs were squashed. Regardless of one's view on Spectre's seriousness, it was a judgement call for Vivaldi alone to make and they made it.
I regard stability in my default browser as THE primary requirement for it. As a result, I never update to a new version immediately the moment it's issued. I accept notification, and start watching reports (especially the blogs) for problems; in a few days, if there are few or none, I manually update - otherwise (as with Vivaldi 1.14), I hold off until an update is issued that fixes the bugs I deem significant. That is me, making my own judgement about my own system's exposure to Spectre risks or whatever other security issue happens to be involved... but I also accept Vivaldi's judgement over when/how to update their own product over which they have the responsibility, just as do all other browser makers.
-
@ian-coog We all know that quality matters. The harsh reality is that you never get a second chance to make a first impression. You can't ever forget that there are (hopefully!) more and more people using Vivaldi for the first time every day and it's critical that their first experience be as good as it can be.
-
@xyzzy And if the first impression is, "I got all my data stolen by using Vivaldi?"
-
@ayespy ?
-
@ayespy said in 1.14 was rushed out without fixing the bugs:
@tjukken Probably not a reinstall (as that action has approximately a 100% rate of changing nothing), but more like a profile refresh or that sort of thing. With a recent update, it seems the default setting of "show drop down when typing" was turned off for some people as well.
OK. Thanks for the tip! "show drop down when typing" was indeed turned off!
-
@quinca71 Maybe she already did... maybe it's "my cat"?
-
Is there anything I can do to make the protocols work again? I mean the magnet, steam and other custom links used to pass info to external programs. I don't really care about any other improvements or security, but I need the protocols to work.
Why release version where something as fundamental as this is broken as the stable? Is there any way I can download older version from before 1.14 when the protocols worked ? I only found 1.14 and then some 1.15 snapshots where in changelog of each it says the protocols are still broken.
edit: also, as a security oriented browser, using Akismet which blocks any post from vpn as spam on your forum...just why?
-
@sammael Maybe because you don't have reputation yet? Other users are posting from VPN (such as the comment directly above yours) without difficulty.
The 1.15 Snapshot already has the protocols fix in it. You can use that, or wait until it comes to Stable.
-
I don't have a clue what "protocols" means, despite me noticing LOTS of people complaining about it/them for weeks/months. I can however explicitly confirm @Ayespy's deduction/recollection/inspection? that i am indeed using a VPN [for years] & it + V in combo continue to work just fine together.