The changelog (for both Brave and Origin) was posted officially in the Brave Community. You can view a screenshot of the bug fixes below.

This is a list of the problems the company has addressed with this release:

1. Fixed a problem with the color picker tool: When creating a new user profile in the browser, the color selection box sometimes appeared outside the screen or in the wrong place. This issue has now been fixed, so choosing a color profile no longer has such issues.

2. Fixed an annoying icon glitch on Windows: On Windows systems, when using vertical tabs, the Brave icon used to get stuck in the title bar right after launching the browser. Now, this has been fixed. For users who use vertical tabs, this was a much-needed improvement.

3. Updated to a newer version of Chromium: The core engine has been updated to version 150.0.7871.128, which brings better security, performance, and the latest fixes.

If your browser hasn’t automatically updated to the latest version yet, you can head to Settings -> About Brave, and wait for the browser to finish updating. Following this, you’ll need to restart your browser.

I’ve checked for this update myself, and sure enough, it began updating immediately to v1.92.141 after opening the About section.

In comparison to the previous update, v1.92.140 (which we detailed here), this one isn’t as feature-heavy. It’s largely just bug fixes and an update to Chromium.

In other Brave news, the New Tab pages also got fresh new wallpapers. More on that here.

The post Brave 1.92.141 is rolling out with minor fixes and a Chromium update appeared first on PiunikaWeb.

DuckDuckGo is now actively endorsing this bill in the opinion piece, urging that the bill be passed swiftly. It’s also supported by Bull Moose Project, Digital Progress Institute, and Public Knowledge.

In other DuckDuckGo news, it recently got a built-in Ad Blocker for YouTube and other video platforms. We covered that here.

The post DuckDuckGo wants to end Google’s power to be your default search engine appeared first on PiunikaWeb.

helium still supports mv2 extensions btw

— Helium (@heliumbrowser) July 15, 2026

Under the post linked above, someone presented a query regarding the security compared to Brave. While several replies from the thread are now deleted, the developer of Helium (@uwukko on X) has left various replies that are still up. He claimed that Helium has a “higher quality” fingerprint noising (though it has fewer APIs).

For those unaware, fingerprinting is a process where browsers quietly collect some of your data. For example, your screen size and resolution, fonts, audio processing, time zone, language, and a lot more. Put together, this can create a “fingerprint” that can uniquely identify you across websites. This occurs even if you clear your cookies or use private browsing.

“Noising” is the process of deliberately providing random values/fake values to the collected details, which ultimately makes tracking across sites much harder.

From what I can infer, the Helium developer also claimed that a certain website (presumably Cover Your Tracks) is “snake oil,” and that hardware acceleration cores are randomized in a way that the site doesn’t expect. Furthermore, he asked for a proper technical report from someone more educated on the topic.

The bottom line is that such test results can be inconsistent for Helium. This is because the browser randomly spoofs details about hardware acceleration in a “stealthy” way. Since trackers can’t easily flag the data as fake, fingerprinting is affected overall. The testing website (Cover Your Tracks) is probably not designed to identify this technique. As a result, it may wrongly identify the fingerprint as “unique,” even when it’s actually not.

Titled “Summer fixes,” an official blog post from the company details the long list of patches in this snapshot release. You can view a snippet of the changelog in the image below.

This is a simplified list of the important changes:

1. AutoHide Bar has now been fixed, so it doesn’t activate randomly when moving buttons. Additionally, issues with dragging it while a pop-up window is open have also been fixed.

2. Calendar: Multi-day events used to overlap incorrectly before, but now that has been addressed.

3. The Chromium version has been updated to 150.0.7871.175, bringing important security and stability improvements.

4. Some issues with crashing when entering the full-screen mode have also been resolved.

5. Enterprise & Business: Better handling of VPN policy conflicts, and fixes bugs with “SyncDisabled.”

6. Moving to experiments, the Reader Mode seems to be enabled by default for internal Vivaldi pages on the browser. There’s also a new flag for horizontally pinned tabs.

7. An issue with favicons not restoring properly when resuming a session has been fixed, and sometimes, favicons would not show up on pages with a “#” in the URL; that has also been addressed.

8. Various other issues with Mail, PWAs, Settings, Quick Commands, and more have been solved.

Note: A snapshot release for Vivaldi isn’t intended for daily use, since it’s a preview of upcoming features and fixes. If you’re a developer/tester and are interested in trying out the preview release, you can grab the download links from here.

Since people were heavily complaining about stability and bugs in Vivaldi, a lot of the issues should be solved once the changes from this snapshot version go live for the public. A lot of people also attributed the stability issues to Vivaldi’s entire interface and customization being based on a Chromium extension, as we detailed in previous coverage.

The frustration is not new. We reported last month that Spaces had been pushed to early July, following confirmation from a moderator in the Dia subreddit. The feature still has not arrived. Users are also waiting for other requested additions, including Little Arc-style windows.

That said, Dia has released something more substantial in between. The Reports feature arrived in an earlier update, giving users a way to turn information into formatted documents. But that release also brought the same question back into focus. When is Dia going to work on the features people have been asking for?

The presentation of version 1.40.1 does not help much. The Reddit post clearly lists the two performance changes, but Dia’s own release notes page does not appear to showcase them. Instead, it highlights app connectors and walks through a Granola and Notion example.

That is the whole changelog. Vivaldi describes both as “regression” fixes, so these were not old problems it had finally gotten around to. They cropped up with the recent release and needed tidying up.

I loaded up the latest Vivaldi update on my Android device and can confirm that neither of the two issues is present. So it’s safe to assume that the bugs have been taken care of.

Android users only got the main 8.1 update a day ago. That one was a bit more interesting, mostly because it finally lets people change the app icon. There are 20 alternatives now, from plain color options to stranger ones that look like wood or camouflage. We covered those additions, along with the new PDF setting, in our article that you can read here.

The PDF option is probably more useful than the icons. It lets you decide whether a PDF opens inside Vivaldi or gets handed to another app. There is also a reset button for the default search engines.

This latest update does not add to any of that. It is just there to make 8.1 behave properly. If you never browse with your phone in landscape, you may not notice a difference at all. But the missing status bar is the sort of bug that can make an app feel unfinished, even when everything else works.

Vivaldi has had a busy few days on the browser side. It recently said its own ad blocker is due for improvements, although the company still has not said what those changes will be or when they will arrive. That is worth keeping an eye on with the old version of uBlock Origin gradually losing support in Chromium browsers.