Update to Chromium 136 – Vivaldi Browser snapshot 3679.3

[Pathduck]

@Ruarí Interestingly, I have two Mv2 extensions, and after the update it failed twice to start. Started on the third attempt. Might be magical thinking but it kind of seems related if the Mv2 extension warnings are involved.

Anyway, after launching properly I went to chrome://flags and disabled the following flags:
chrome://flags/#extension-manifest-v2-deprecation-warning
chrome://flags/#extension-manifest-v2-deprecation-disabled
chrome://flags/#extension-manifest-v2-deprecation-unsupported

It now seems to launch properly.

[DoctorG]

Regression: Visited Links do not change color by CSS

Sees related to a new "feature" https://developer.chrome.com/blog/visited-links

Bad for web development.

[Ruarí]

Quick fix build for Linux and macOS added (and autoupdate re-enabled for those two platforms). Windows will be done later.

[Linu74]

@Pathduck said in Update to Chromium 136 – Vivaldi Browser snapshot 3678.3:

@Ruarí Interestingly, I have two Mv2 extensions, and after the update it failed twice to start. Started on the third attempt. Might be magical thinking but it kind of seems related if the Mv2 extension warnings are involved.

Anyway, after launching properly I went to chrome://flags and disabled the following flags:
chrome://flags/#extension-manifest-v2-deprecation-warning
chrome://flags/#extension-manifest-v2-deprecation-disabled
chrome://flags/#extension-manifest-v2-deprecation-unsupported

It now seems to launch properly.

I followed your Steps and now the latest Snapshot starts on my MacOS Setup.

Linu74

[Ruarí]

@pnnl: Thanks

[Pathduck]

[Panels] Unify appearance of History with Windows and Tabs (VB-116530)

Seems to not account for dark themes:

History uses a different theme colour:

#history-panel .vivaldi-tree .tree-row {
    height: 100%;
    padding-inline: 3px;
    background-color: var(--colorBgLighter);
    border-radius: unset;
}

.theme-dark #window-panel .vivaldi-tree .tree-row {
    background-color: var(--colorBgDark);
}

[NECOdes]

@ruarí: --disable-extensions works.
Might've caused by Sync Extension Settings
Will wait for a fix.

[Ruarí]

@helsten2: download and try again. Also check your disk space.

[AllanH]

@Pathduck said in Update to Chromium 136 – Vivaldi Browser snapshot 3678.3:

@Ruarí Interestingly, I have two Mv2 extensions, and after the update it failed twice to start. Started on the third attempt. Might be magical thinking but it kind of seems related if the Mv2 extension warnings are involved.

Anyway, after launching properly I went to chrome://flags and disabled the following flags:
chrome://flags/#extension-manifest-v2-deprecation-warning
chrome://flags/#extension-manifest-v2-deprecation-disabled
chrome://flags/#extension-manifest-v2-deprecation-unsupported

It now seems to launch properly.

This worked for me also.

[ugly]

@Ruarí said in Update to Chromium 136 – Vivaldi Browser snapshot 3678.3:

Quick fix build for Linux and macOS added (and autoupdate re-enabled for those two platforms). Windows will be done later.

I had the startup crash on Linux with the previous update. Got the new update, and it started okay. Everything seems okay now. Thanks for the quick fix.

[ender85]

If you have manifest V2 extensions, for now at least you can import this .reg file to re-enable them. Once this stops working, I'll probably switch to Firefox.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Vivaldi]
"ExtensionManifestV2Availability"=dword:00000002

Address bar is still completely broken – typing an address sends it to the default search provider unless I hit Esc first (VB-116556).

[helsten2]

@ruarí: Thanks. I downloaded the full package, and the install seemed to work. However, Vivaldi won't start. I just re-installed the previous version and "all is good" ...

[ender85]

BTW, if anybody needs, I converted Chrome 136 ADMX templates for use with Vivaldi (mostly just search & replace): https://eternallybored.org/misc/vivaldi/vivaldi_admx_templates.7z

[DoctorG]

@ender85 Thanks.

[nutcracker]

@allanh: But without any extensions

[AllanH]

@nutcracker All my extensions are working fine at the moment.
My Manifest v2 extensions are loaded as unpacked extensions.

[Aaron]

@Ruarí Why is it back?

[Pathduck]

@Aaron Because of the quick fixes released for Linux and MacOS I guess?
Not for Windows yet far as I can tell.

[nutcracker]

@allanh: I did everything you suggested and I found no extensions at all in my extensions list, packed or unpacked. In fact by doing those alterations in chrome://flags I have a simulation of opening vivaldi with no extensions, i.e. like starting as vivaldi.exe --disable-extensions. Do I have to reactivate any single one of my 67 extensions in my profile by loading them as unpacked?

[DoctorG]

GPU process crashed
Weird. vivaldi://gpu gives at end
Log Messages
GpuProcessHost: The info collection GPU process exited normally. Everything is okay.
GpuProcessHost: The GPU process crashed!

Something really wrong with the Vivaldi on Chromium 138.