Update to Chromium 136 – Vivaldi Browser snapshot 3679.3

[Folgore101]

@DoctorG All green ones work, only 3 gray 3 work. I see no difference with Firefox.

[DoctorG]

@Folgore101 Which GPU?
HWA active for GPU on video decode (see vivaldi:gpu)?

[yngve]

@DoctorG No idea, although you have, if I understand this correctly, already confirmed the issue in Chrome 136 and reported upstream.

As far as the various video streams are concerned, you should look at which video formats they are using (which works, which doesn't). That might even include DRM vs. no DRM. IOW: What is different?

I would not put too much weight on Firefox working, since it is a different engine, and thus have different code handling the hardware acceleration interface.

It might be more of interest that Edge works, as opposed to Vivaldi w/136 and (if I understand correctly) Chrome 136, which doesn't.

I'll note that Vivaldi do pass certain video formats to the Windows Media system which handles decoding, instead of the Chromium engine's decoders for that format (which is why looking at which formats are used is going to be important).

[DoctorG]

@yngve said in Update to Chromium 136 – Vivaldi Browser snapshot 3679.3:

I'll note that Vivaldi do pass certain video formats to the Windows Media system which handles decoding

Yes, and i guess that is the issue on my Windows for Chromium 136 related Vivaldi.

[yngve]

@DoctorG Only H264 encoded video is passed to Windows Media

[DoctorG]

@yngve I do not know what changes in Chromium 136 were done resulting in broken GPU video HWA.

[yngve]

@DoctorG I was not asking you for what changed in Chromium (only referring to the bug you reported to Chromium BTS); instead I was asking about differences in the video formats used by the working sites vs. the one(s) that doesn't work (e.g H264 vs AV1, DRM vs. no DRM).

[yngve]

@DoctorG For reference, I ran a few of the tests on the site you linked to, the green banded video ones seemed to work for me (Nvidia RTX 3060; HWA enabled).

If only some are failing, we need to know precisely which ones.

(Rule 1: Make sure the right binary is being run (oops!); but that didn't change anything on my config, for the videos I tested, at least.)

[Folgore101]

@DoctorG
Windows 11 24H2
NVIDIA GeForce RTX 4070 Ti - Driver 576.02
Video Decode: Hardware accelerated
Video Encode: Hardware accelerated

[JustABrowser58]

Seems like the Windows 64-bit version has finally been uploaded (or reuploaded), and it seems like the video playing bug is fixed for me now

[cuiliang]

chrome.userScripts.configureWorld({
messaging: true
});
Not supported.
https://developer.chrome.com/docs/extensions/reference/api/userScripts#work_in_isolated_worlds

[sjudenim]

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

Judging by some of the comments, a quick reminder, might be needed, our own ad blocker does not require manifest v2 support to work and is still being actively improved.

https://vivaldi.com/blog/manifest-v3-update-vivaldi-is-future-proofed-with-its-built-in-functionality/

I'm not going to speak for anyone else, but my issue isn't whether the integrated ad blocker will run with MV3 but how effective it can be with the limitations that come with the change

[Hadden89]

This post is deleted!

[Pesala]

Wherever I have tried it, Site Settings opens a blank page.

• Click the padlock icon in the URL field
• Click on Site Settings

Tested here or forum.vivaldi.net, on YouTube, and the High-Logic forum:

vivaldi:settings/content/siteDetails?site=https%3A%2F%2Fforum.high-logic.com

Disabling the AdGuard Adblocker extension makes no difference. Also happens in a Private Window.

[Folgore101]

@Pesala They are already aware.

@iAN-CooG said in Update to Chromium 136 – Vivaldi Browser snapshot 3679.3:

clicking on the padlock to see site settings for example on this site all I obtain is going to
chrome://settings/content/siteDetails?site=https%3A%2F%2Fforum.vivaldi.net
and a blank page
Can anyone confirm?

edit: even going to just
chrome://settings
only a blank page is shown

@DoctorG said in Update to Chromium 136 – Vivaldi Browser snapshot 3679.3:

@iAN-CooG Known issue and already in bug tracker.

[ZzZombo]

In this snapshot you may get a warning about certain key extensions being disabled.

Why the ... was this not put into the changelog??? Previously you'd put such disclaimers for way less important things.

Now onto finding how do I downgrade to the previous version... I can't live w/o TamperMonkey, uBlock Origin and a dozen of other extensions, some of which have nothing to do with ad-blocking.

modedit: language.
The Code of Conduct for Vivaldi's community asks its members to stay polite and respectful.
https://vivaldi.com/privacy/code-of-conduct/
We kindly ask you to tone down your language.

[Pathduck]

@ZzZombo Because when testing Snapshots it's implied that bugs will happen. You might lose data, it might crash, it might nuke your profile.

If you cannot deal with bugs, crashes and dataloss without throwing a fit I suggest you stick with Stable releases.

Downgrading is not supported and it will break your profile.

And you will have to accept that come July/August all your Manifest v2 extensions will be gone, so you better start looking for alternatives.
Tampermonkey is Mv3 though so it will not be affected.