Minor update (2) for Vivaldi 2.0
Today’s minor update to Vivaldi 2.0 resolves issues with undeletable cookies.
Click here to see the full blog post
Good to see the update, less good to see that this will break people's ability to use that keep extension. I don't use it myself, but from the channels it seems pretty popular.
I wonder what that cookie's fortune is. "Vous allez... de..."
"Vous allez utiliser Vivaldi au lieu de chrome" peut-être ?
iAN CooG last edited by
@lonm this update is intended to FIX that regression, I guess.
@lonm: We can see a bit of the translation on the other side : "You will..."
It's not very helpful tho
spideymang last edited by
Thanks for the updates, You rock!!
Last week I reported a bug with ticket number VB-44692 and you fixed it!!!
Love the support, you always listen to the audience
Chas4 last edited by
Getting a crash on close of Vivaldi
Chas4 last edited by
@chas4: Set to use native window and the crash disappeared. For Facebook videos if you pause the video to long Vivaldi will no longer player the audio, the video still plays but with no audio (mute and volume controls do nothing).
Ornorm last edited by
@lonm Excellent! (Vous allez utiliser Vivaldi au lieu de chrome)
What do you mean by
less good to see that this will break people's ability to use that keep extension
I haven't seen anything into the article stating anything in particular. Can you please explain a bit more? Thanks in advance.
@ornorm The full explanation is complicated, but the basic problem is that Google Keep expects to be installed in Google Chrome and expects that the underlying Google Sync be functional and able to talk to Google's servers regardless of whether or not you actually use their Sync service. Vivaldi tries to disable upstream connections to Google, and does what it can to prevent Google's auth cookies from getting set... and all the things that needed to be done to disable Account Consistency in Vivaldi made the Google Keep extension unhappy. In the end, it's really a bug in Google Keep and something that Google is unlikely to fix.
Pesala last edited by Pesala
Updated OK without having to manually restart Vivaldi.
The Remove Tab Spacing in Maximized Windows* setting was not respected on restart. It was on the next restart.
Ornorm last edited by Ornorm
@xyzzy Thank you very much for the time you've taken to give this explanation. I didn't understood it was about Google Keep. I thought it was all extensions in general so I was afraid of updating to the new version.
Thanks a lot. I can now update! Let's go for it.
Edit : ok, after reading the blog post again, I understand now. All this just because of keep instead of Keep which was confusing for me...
@ornorm I think I misread the changelog there.
bekam last edited by
No update the chromium engine?.
Pesala last edited by
@bekam There won't be updates to the Chromium engine for old version. Too much would break. A lot of development time is spent fixing things broken by Chromium updates.
ericmchen last edited by
Bug VB-44421, which is reported by me, still exists as of this update... Please fix it ASAP. It crashes whenever I open up speaker notes in Google Slides
@ericmchen Thanks. I've reproduced the crash and added my own confirmation to the bug.
Steffie last edited by
I do not understand these statements:
Today’s minor update to Vivaldi 2.0 resolves issues with undeletable cookies
[Regression] Google sign-in cookies are being set in Vivaldi and cannot be cleared
I've read similar stuff in recent Snapshots. Yet, despite these, all the time, these persist in my Snapshot & Stable [respectively]:
I delete them, i block them, yet they constantly rise from the dead. Either the putative fixes don't work, or i'm fundamentally misunderstanding what is intended. Help pls?
@steffie I'll have to double-check with the devs but based on what I know about the fixes, the changes in this build neuters some underlying Google code and prevents the auth cookies from getting set... but once set, I think you'll need additional changes coming up in the next major Stable release (based on Chromium 70) to actually clear the stored cookies and site data.
@steffie Also, the latest Snapshot should allow these auth tokens to get cleared... unless you're Syncing between Snapshot and Stable and perhaps that's causing them to resurrect?? (...although I don't think that's possible.)