Update version of Chromium
-
I've been using Vivaldi for a while, but for the past few weeks, Google Docs notify me that my browser is not supported and Google Meet won't work at all as my browser is out of date.
This is more than likely an issue with the version of Chromium that Vivaldi is using. Is there any way to keep this up to date? Opera usually has weekly releases even if it's just to update Chromium.
-
Usually also Vivaldi Snapshots builds are weekly (even multiple times a week sometimes) but as of now current snapshot is a couple of weeks old due to a major rewrite in the windows management IIRC. It will be updated "Soon" (TM).
-
I use the Random User Agent, which works great, but is thought more for reasons of privacy, as it does not disguise only the browser, but also the OS.
Apart from this, Google Docs works without problems in Vivaldi, simply ignoring and closing this notice of 'incompatibility'
-
@dleon said in Update version of Chromium:
For Google Meet
You could use any UserAgent (UA) Switcher extension for bypass that "Unsupported" page.I need to add this real current GChrome UA, I'm in Linux;
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36
Opera could pass it somehow. I tried to use their current Stable UA but not working.
For Google Docs, do you see anything not working after you ignore that warning?
That warning also not show up if I use UA trick above.The user agent string trick worked. I had tried that before, but somehow did something wrong. Thanks for the tip!
-
The new version of Chrome forces Vivaldi to change how they handle their window, that's why they haven't released a new snapshot recently. They are working on it, but it is a big change - internally. (Admittedly, if they get it right you won't be able to tell the difference. But that's where we are at the moment.)
-
@dleon The Vivaldi window is an app. Chromium is planning to remove support for apps on all platforms except ChromeBook. Vivaldi must account for that.
-
@ayespy Do you know exactly how they are planning on doing this? If Vivaldi can no longer run as a Chrome app, then wouldn't that require a major, major rewrite/refactor?
Also, I wonder if this work will help performance and memory consumption? I know that Vivaldi's Chrome app process by itself takes over a GB of RAM for me. If their work will allow them to put the browser's UI into the main browser process, I would imagine we would see some benefits.
-
Chromium's blog publicly announced the Chrome app deprecation timeframe back in August 2016 with a completion around early 2018... but my guess is that it was almost certainly being discussed amongst chromium developers before August. While the timeframe is not "sudden", it does appear rather short for the rework into whatever form it seems would now be required for a complex 'app' like Vivaldi. I really, really hope Vivaldi's devs can pull off this transition without a lot of grief or functionality loss.
