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 -
@iAN-CooG It has already been reported and should be resolved in the internal version.
-
My custom menus got reset to default.
Wtf Vivaldi? -
@iAN-CooG Known issue and already in bug tracker.
-
@pathduck: Many thanks. I can now use Vivaldi again. I also opened a bug report (VB-116763) and attached zipped .dmp files from the CrashPad folder, so hopefully that's what they needed and they can get this fixed quickly.
-
Said:
I just installed AdGuard AdBlocker.
You can reuse your “My filters” and “Trusted sites” lists directly, just copy and paste in “User rules” and “Allowlist” respectively.
To reuse what you have accumulated in “My rules” (Dynamic Filtering):
This :
and this:
It requires a bit of “Find and Replace” in Notepad++ and a bit of Excel magic, but it doesn't take more than 15 minutes.
-
@yngve Can you tell why with HWA video streams of TV stations play, but HTML 5 videos from https://tools.woolyss.com/html5-audio-video-tester/ fail?
Can not be my graphics driver.
Windows 11 23H2Edge 136 and Firefox 138 work.
-
How can these regressions still be outstanding after so long? Regressions should be fixed before the next stable build.
- VB-97070 Panel Toggle button is on Navigation Toolbar, but on Panel Toolbar Edit Dialog (27/4/2023)
- VB-112536 Status Bar Clock Always Displays Timer Name (16/12/2024)
-
@DoctorG All green ones work, only 3 gray 3 work. I see no difference with Firefox.
-
@Folgore101 Which GPU?
HWA active for GPU on video decode (see vivaldi:gpu)? -
@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).
-
@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.
-
@DoctorG Only H264 encoded video is passed to Windows Media
-
@yngve I do not know what changes in Chromium 136 were done resulting in broken GPU video HWA.
-
@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).
-
@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.)
-
@DoctorG
Windows 11 24H2
NVIDIA GeForce RTX 4070 Ti - Driver 576.02
Video Decode: Hardware accelerated
Video Encode: Hardware accelerated -
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
-
chrome.userScripts.configureWorld({
messaging: true
});
Not supported.
https://developer.chrome.com/docs/extensions/reference/api/userScripts#work_in_isolated_worlds -
@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.
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