Minor update (2) for Vivaldi 2.0

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

@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...

LonM

@ornorm I think I misread the changelog there.

bekam

@ruario
No update the chromium engine?.

Pesala

@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.

Critical security fixes may be back-ported.

ericmchen

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

xyzzy

@ericmchen Thanks. I've reproduced the crash and added my own confirmation to the bug.

Steffie

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?

xyzzy

@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.

xyzzy

@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.)

Steffie

@xyzzy Thanks for the fast response. I do NOT use Sync... so that cannot be a factor. As i said, i manually delete those damn google ones, i also add them to the blocked cookies list. Yet after relaunching either of my V's, per my pics above, they have returned.

QuHno

@steffie
This screenshot was taken after I have closed all tabs that use google services and restarted the browser with the setting "empty cookies (apart from some whitelisted) on exit":

As you can see there is no more google-ish stuff inside.

Works for me if I:

close all pages that use e.g. the google services such as fonts or analytics or adwords or apis and empty the cookies.
block all google related cookies.
empty all cookies on exit as long as I don't have a page open that uses google services (if I don't block them, that is)

Every measure from above works on its own. For me it is fixed.

Of course it can't work if you:

still have pages from the last session that use any google services - which are almost all bigger sites ITW nowadays
don't block the scripts on pages that insert google IFRAMES, which of course set their cookies again as soon as the tab is activated
have a panel that contains such stuff
use extensions that load google fonts or apis, or connect to anylytics.

Steffie

@quhno Many thanks for testing, then posting your results. I can confirm that if i disable all my extensions, explicitly block all those google cookies, manually clear all current non-whitelisted cookies, then restart Stable, initially there's no google cookies show up in the filtered list. However, within a minute max of browsing my regular sites then rechecking, several of the google cookies have returned. So much for blocking.

Given that i do not shutdown my pc each night but merely suspend/sleep it, & V [+ my other daily pgms] remain open prior to sleep, the practical upshot is that several days easily elapse where these re-re-re-reborn google cookies exist.

Given that i rely heavily on my suite of extensions, & given the practical ineffectiveness re google cookies per above even with all extensions disabled anyway, i re-enabled them all but one by one, having first [again] manually cleared all google cookies, & carefully rechecked the cookies status after each extension was re-enabled. I found the following strong associations; take note of the 2nd one, which IMO is deeply deeply ironic:

I've now replaced VCM with Cookie AutoDelete, but it also is unable to control those rotten google cookies. It has a benefit though of being able to intelligently do what its name says, at intervals i specify [42"], apart from those i whitelist. So that keeps all other cookies under control wrt my as-mentioned uptimes typically of many many days but the google ones are hopeless still.

I wrote above of tonight's testing with Stable, but the same applies to my Snapshot. I've pretty much given up...

QuHno

@steffie Guess which extension will be the first to set a cookie for either analytics or the extension updater again
The reason why mine don't is because I have either written my own, or removed that crap, or got mine from people (not companies) I know and trust.

Other than that: I have those 2 domains in my HOSTS since ages. 0.0.0.0 is such a nice address for them to resolve (127.0.0.0 of course too, but I have something listening on that) because I really don't need them, I am not planning to visit them in the next 10 years or so

AtoZStamps

@ruario I cannot open Vivaldi at all now after yesterday's update. Even with a full shutdown and restart. Back to Chrome?

xyzzy

@atozstamps Did you try uninstalling and going back to the previous Vivaldi 2.0 build? The Vivaldi team has suspended updates and has now made the previous version (2.0.1309.37) available again on the main download page: https://vivaldi.com/download/

Edit: A new Vivaldi 2.0 update has now been released: https://vivaldi.com/blog/minor-update-3-for-vivaldi-2-0/

MarkJansen

@xyzzy: New to Vivaldi and just found this answer. Thank you for the clear and thorough explanation! I'd read quite a few pages before finding your response and finally feel like I understand what's happening. Cheers!